Capability of Positioning Service Level for Wireless Device

ABSTRACT

A gateway mobile location center (GMLC) may include processor(s) and memory storing instructions. The instructions, when executed by the processor(s), may cause the GMLC to perform operations that include receiving, from a location services (LCS) client, a request for a capability of a positioning service level for a wireless device. The operations may also include receiving, from a network function, a second message indicating at least one of: a positioning capability of the wireless device; and a positioning capability of at least one base station. The operations may further include determining the capability of the positioning service level for the wireless device, based on the second message. The operations may additionally include sending, by the GMLC to the LCS client, a response that includes the capability of the positioning service level. The capability of the positioning service level may include a parameter indicating an absolute or a relative positioning.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. application Ser. No.17/323,546, filed May 18, 2021, which claims the benefit of ProvisionalApplication No. 63/026,420, filed May 18, 2020, all of which are herebyincorporated by reference in their entireties.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

Examples of several of the various embodiments of the present inventionare described herein with reference to the drawings.

FIG. 1 is a diagram of an example 5G system architecture as per anaspect of an embodiment of the present disclosure.

FIG. 2 is a diagram of an example 5G System architecture as per anaspect of an embodiment of the present disclosure.

FIG. 3 is a system diagram of an example wireless device and a networknode in a 5G system as per an aspect of an embodiment of the presentdisclosure.

FIG. 4 is a system diagram of an example wireless device as per anaspect of an embodiment of the present disclosure.

FIG. 5A and FIG. 5B depict two registration management state models inUE 100 and AMF 155 as per an aspect of embodiments of the presentdisclosure.

FIG. 6A and FIG. 6B depict two connection management state models in UE100 and AMF 155 as per an aspect of embodiments of the presentdisclosure.

FIG. 7 is diagram for classification and marking traffic as per anaspect of an embodiment of the present disclosure.

FIG. 8 is an example call flow for registration procedure as per anaspect of an embodiment of the present disclosure.

FIG. 9 is an example call flow for registration procedure as per anaspect of an embodiment of the present disclosure.

FIG. 10 is an example call flow for service request procedure as per anaspect of an embodiment of the present disclosure.

FIG. 11 is an example call flow for service request procedure as per anaspect of an embodiment of the present disclosure.

FIG. 12 is an example call flow for PDU session establishment procedureas per an aspect of an embodiment of the present disclosure.

FIG. 13 is an example call flow for PDU session establishment procedureas per an aspect of an embodiment of the present disclosure.

FIG. 14 illustrates an example mobile communication networks as per anaspect of an embodiment of the present disclosure.

FIG. 15 is a diagram of an example 5G policy and charging control systemarchitecture as per an aspect of an embodiment of the presentdisclosure.

FIG. 16 is an example call flow for PDU session establishment chargingas per an aspect of an embodiment of the present disclosure.

FIG. 17 is a first example arrangement of a local location managementcomponent (LMC) associated with a base station as per an aspect of anembodiment of the present disclosure.

FIG. 18 is a diagram of a second example arrangement of an LMCassociated with a base station as per an aspect of an embodiment of thepresent disclosure.

FIG. 19 is a third example arrangement of an LMC associated with a basestation as per an aspect of an embodiment of the present disclosure.

FIG. 20 is a diagram of an example architecture for location service asper an aspect of an embodiment of the present disclosure.

FIG. 21 is an example diagram depicting Performance requirements fordifferent positioning service levels as per an aspect of an embodimentof the present disclosure.

FIG. 22 is an example diagram depicting definition of aparameter/information element for the positioning capability informationas per an aspect of an embodiment of the present disclosure.

FIG. 23 is an example diagram depicting a ProvideCapabilities messagebody as per an aspect of an embodiment of the present disclosure.

FIG. 24 is an example diagram depicting a REGISTRATION REQUEST messagebody as per an aspect of an embodiment of the present disclosure.

FIG. 25 is an example diagram depicting a Positioning Capability Reportmessage body as per an aspect of an embodiment of the presentdisclosure.

FIG. 26 is an example diagram depicting the procedures of a GMLC as peran aspect of an embodiment of the present disclosure.

FIG. 27 is an example call flow as per an aspect of an embodiment of thepresent disclosure.

FIG. 28 is an example diagram depicting the procedures of an AMF as peran aspect of an embodiment of the present disclosure.

FIG. 29 is an example call flow as per an aspect of an embodiment of thepresent disclosure.

FIG. 30 is an example call flow as per an aspect of an embodiment of thepresent disclosure.

FIG. 31 is an example call flow as per an aspect of an embodiment of thepresent disclosure.

DETAILED DESCRIPTION

Example embodiments of the present invention enable implementation ofenhanced features and functionalities in 5G systems. More particularly,the embodiments of the technology positioning service level and servicearea control (e.g. for 5G or future communication system). Throughoutthe present disclosure, UE, wireless device, vehicle terminal, andmobile device are used interchangeably. Throughout the presentdisclosure, base station, (Radio) Access Network ((R)AN), NextGeneration Radio Access Network (NG-RAN), New radio Node B (gNB), NextGeneration eNodeB (ng-eNBs) are used interchangeably. Throughout thepresent disclosure, base station, Radio Access Network (RAN), eNodeB areused interchangeably.

Throughout the present disclosure, AMF, LMC, LMF, UDM, OAM, GMLC, LCSclient, NEF and AF are example network functions which may beimplemented either as a network element on a (dedicated) hardware,and/or a network node as depicted FIG. 4 , or as a software instancerunning on a (dedicated) hardware and/or shared hardware, or as avirtualized function instantiated on an appropriate platform.

The following acronyms are used throughout the present disclosure:

-   -   5G 5th generation mobile networks    -   5GC 5G Core Network    -   5GS 5G System    -   5G-AN 5G Access Network    -   5QI 5G QoS Indicator    -   ACK Acknowledgement    -   AF Application Function    -   AMBR Aggregate Maximum Bit Rate    -   AMF Access and Mobility Management Function    -   AN Access Network    -   ANDSP Access Network Discovery & Selection Policy    -   APN Access Point Name    -   ARP Allocation and Retention Priority    -   BD Billing Domain    -   BPS Barometric Pressure Sensor    -   CCNF Common Control Network Functions    -   CDR Charging Data Record    -   CHF Charging Function    -   CIoT Cellular IoT    -   CN Core Network    -   CP Control Plane    -   C-V2X Cellular Vehicle-To-Everything    -   DAB Digital Audio Broadcasting    -   DDN Downlink Data Notification    -   DDoS Distributed Denial of Service    -   DL Downlink    -   DN Data Network    -   DN-AAA Data Network Authentication Authorization and Accounting    -   DNN Data Network Name    -   DTMB Digital Terrestrial Multimedia Broadcast    -   ECGI E-UTRAN Cell Global Identifier    -   ECID Enhanced Cell Identity    -   E-CSCF Emergency Call Session Control Function    -   eNodeB evolved Node B    -   EPS Evolved Packet System    -   E-UTRAN Evolved Universal Terrestrial Radio Access Network    -   FDD Frequency Division Duplex    -   FQDN Fully Qualified Domain Name    -   F-TEID Fully Qualified TEID    -   GAD Geographical Area Description    -   GMLC Gateway Mobile Location Centre    -   gNB Next Generation Node B    -   gNB-CU-CP gNB Central Unit Control Plane    -   GNSS Global Navigation Satellite System    -   GPSI Generic Public Subscription Identifier    -   GTP GPRS Tunneling Protocol    -   GUTI Globally Unique Temporary Identifier    -   GW Gateway    -   HGMLC Home GMLC    -   HTTP Hypertext Transfer Protocol    -   ID Identifier    -   IMEI International Mobile Equipment Identity    -   IMEI DB IMEI Database    -   IMS IP Multimedia Subsystem    -   IMSI International Mobile Subscriber Identity    -   IP Internet Protocol    -   IP-CAN IP Connectivity Access Network    -   L2 Layer 2 (data link layer)    -   L3 Layer 3 (network layer)    -   LADN Local Area Data Network    -   LAN local area network    -   LCS LoCation Services    -   LI Lawful Intercept    -   LMC Location Management Component    -   LMF Location Management Function    -   LPP LTE Positioning Protocol    -   LRF location retrieval function    -   MAC Media Access Control    -   MEI Mobile Equipment Identifier    -   MICO Mobile Initiated Connection Only    -   MME Mobility Management Entity    -   MO Mobile Originated    -   MO-LR Mobile Originated Location Request    -   MSISDN Mobile Subscriber ISDN    -   MT Mobile Terminating    -   MT-LR Mobile Terminated Location Request    -   N3IWF Non-3GPP InterWorking Function    -   NAI Network Access Identifier    -   NAS Non Access Stratum    -   NAT Network address translation    -   NB-IoT Narrow Band IoT    -   NCGI NR Cell Global Identity    -   NEF Network Exposure Function    -   NF Network Function    -   NGAP Next Generation Application Protocol    -   ng-eNB Next Generation eNB    -   NG-RAN NR Radio Access Network    -   NI-LR Network Induced Location Request    -   NR New Radio    -   NRF Network Repository Function    -   NRPPA New Radio Positioning Protocol A    -   NSI Network Slice Instance    -   NSSAI Network Slice Selection Assistance Information    -   NSSF Network Slice Selection Function    -   NWDAF Network Data Analytics Function    -   OAM Operation Administration and Maintenance    -   OCS Online Charging System    -   OFCS Offline Charging System    -   OTDOA Observed Time Difference of Arrival    -   PCC Policy and Charging Control    -   PCF Policy Control Function    -   PCRF Policy and Charging Rules Function    -   PDN Packet Data Network    -   PDU Packet Data Unit    -   PEI Permanent Equipment Identifier    -   PGW PDN Gateway    -   PLMN Public Land Mobile Network    -   ProSe Proximity-based Services    -   QFI QoS Flow Identifier    -   QoS Quality of Service    -   RM Registration Management    -   RA Random Access    -   RAN Radio Access Network    -   RAT Radio Access Technology    -   RRC Radio Resource Control    -   RM Registration Management    -   S1-AP S1 Application Protocol    -   SBA Service Based Architecture    -   SEA Security Anchor Function    -   SGW Serving Gateway    -   SCM Security Context Management    -   SM Session Management    -   SMF Session Management Function    -   SMSF SMS Function    -   S-NSSAI Single Network Slice Selection Assistance information    -   SS Synchronization Signal    -   SSC Session and Service Continuity    -   SUCI Served User Correlation ID    -   SUPI Subscriber Permanent Identifier    -   TA Tracking Area    -   TAI Tracking Area Identity    -   TBS Terrestrial Beacon System    -   TCP Transmission Control Protocol    -   TEID Tunnel Endpoint Identifier    -   TMSI Temporary Mobile Subscriber Identity    -   TNAN Trusted Non-3GPP Access Network    -   TNGF Trusted Non3GPP Gateway    -   TRP Transmission and Reception Point    -   UCMF UE radio Capability Management Function    -   UDR Unified Data Repository    -   UDM Unified Data Management    -   UDP User Datagram Protocol    -   UE User Equipment    -   UL Uplink    -   UL CL Uplink Classifier    -   UPF User Plane Function    -   V2X Vehicle-To-Everything    -   WLAN Wireless Local Area Network    -   XML Extensible Markup Language

Example FIG. 1 and FIG. 2 depict a 5G system comprising of accessnetworks and 5G core network. An example 5G access network may comprisean access network connecting to a 5G core network. An access network maycomprise an NG-RAN 105 and/or non-3GPP AN 165. An example 5G corenetwork may connect to one or more 5G access networks 5G-AN and/orNG-RANs. 5G core network may comprise functional elements or networkfunctions as in example FIG. 1 and example FIG. 2 where interfaces maybe employed for communication among the functional elements and/ornetwork elements.

In an example, a network function may be a processing function in anetwork, which may have a functional behavior and/or interfaces. Anetwork function may be implemented either as a network element on adedicated hardware, and/or a network node as depicted in FIG. 3 and FIG.4 , or as a software instance running on a dedicated hardware and/orshared hardware, or as a virtualized function instantiated on anappropriate platform.

In an example, access and mobility management function, AMF 155, mayinclude the following functionalities (some of the AMF 155functionalities may be supported in a single instance of an AMF 155):termination of RAN 105 CP interface (N2), termination of NAS (N1), NASciphering and integrity protection, registration management, connectionmanagement, reachability management, mobility management, lawfulintercept (for AMF 155 events and interface to LI system), providetransport for session management, SM messages between UE 100 and SMF160, transparent proxy for routing SM messages, access authentication,access authorization, provide transport for SMS messages between UE 100and SMSF, security anchor function, SEA, interaction with the AUSF 150and the UE 100, receiving the intermediate key established as a resultof the UE 100 authentication process, security context management, SCM,that receives a key from the SEA that it uses to derive access networkspecific keys, and/or the like.

In an example, the AMF 155 may support non-3GPP access networks throughN2 interface with N3IWF 170, NAS signaling with a UE 100 over N3IWF 170,authentication of UEs connected over N3IWF 170, management of mobility,authentication, and separate security context state(s) of a UE 100connected via non-3GPP access 165 or connected via 3GPP access 105 andnon-3GPP access 165 simultaneously, support of a coordinated RM contextvalid over 3GPP access 105 and non 3GPP access 165, support of CMmanagement contexts for the UE 100 for connectivity over non-3GPPaccess, and/or the like.

In an example, an AMF 155 region may comprise one or multiple AMF 155sets. The AMF 155 set may comprise some AMF 155 that serve a given areaand/or network slice(s). In an example, multiple AMF 155 sets may be perAMF 155 region and/or network slice(s). Application identifier may be anidentifier that may be mapped to a specific application trafficdetection rule. Configured NSSAI may be an NSSAI that may be provisionedin a UE 100. DN 115 access identifier (DNAI), for a DNN, may be anidentifier of a user plane access to a DN 115. Initial registration maybe related to a UE 100 registration in RM-DEREGISTERED 500, 520 states.N2AP UE 100 association may be a logical per UE 100 association betweena 5G AN node and an AMF 155. N2AP UE-TNLA-binding may be a bindingbetween a N2AP UE 100 association and a specific transport networklayer, TNL association for a given UE 100.

In an example, session management function, SMF 160, may include one ormore of the following functionalities (one or more of the SMF 160functionalities may be supported in a single instance of a SMF 160):session management (e.g. session establishment, modify and release,including tunnel maintain between UPF 110 and AN 105 node), UE 100 IPaddress allocation & management (including optional authorization),selection and control of UP function(s), configuration of trafficsteering at UPF 110 to route traffic to proper destination, terminationof interfaces towards policy control functions, control part of policyenforcement and QoS. lawful intercept (for SM events and interface to LISystem), termination of SM parts of NAS messages, downlink datanotification, initiation of AN specific SM information, sent via AMF 155over N2 to (R)AN 105, determination of SSC mode of a session, roamingfunctionality, handling local enforcement to apply QoS SLAs (VPLMN),charging data collection and charging interface (VPLMN), lawfulintercept (in VPLMN for SM events and interface to LI System), supportfor interaction with external DN 115 for transport of signaling for PDUsession authorization/authentication by external DN 115, and/or thelike.

In an example, a user plane function, UPF 110, may include one or moreof the following functionalities (some of the UPF 110 functionalitiesmay be supported in a single instance of a UPF 110): anchor point forIntra-/Inter-RAT mobility (when applicable), external PDU session pointof interconnect to DN 115, packet routing & forwarding, packetinspection and user plane part of policy rule enforcement, lawfulintercept (UP collection), traffic usage reporting, uplink classifier tosupport routing traffic flows to a data network, branching point tosupport multi-homed PDU session(s), QoS handling for user plane, uplinktraffic verification (SDF to QoS flow mapping), transport level packetmarking in the uplink and downlink, downlink packet buffering, downlinkdata notification triggering, and/or the like.

In an example, the UE 100 IP address management may include allocationand release of the UE 100 IP address and/or renewal of the allocated IPaddress. The UE 100 may set a requested PDU type during a PDU sessionestablishment procedure based on its IP stack capabilities and/orconfiguration. In an example, the SMF 160 may select PDU type of a PDUsession. In an example, if the SMF 160 receives a request with PDU typeset to IP, the SMF 160 may select PDU type IPv4 or IPv6 based on DNNconfiguration and/or operator policies. In an example, the SMF 160 mayprovide a cause value to the UE 100 to indicate whether the other IPversion is supported on the DNN. In an example, if the SMF 160 receivesa request for PDU type IPv4 or IPv6 and the requested IP version issupported by the DNN the SMF 160 may select the requested PDU type.

In an example embodiment, the 5GC elements and UE 100 may support thefollowing mechanisms: during a PDU session establishment procedure, theSMF 160 may send the IP address to the UE 100 via SM NAS signaling. TheIPv4 address allocation and/or IPv4 parameter configuration via DHCPv4may be employed once PDU session may be established. IPv6 prefixallocation may be supported via IPv6 stateless autoconfiguration, ifIPv6 is supported. In an example, 5GC network elements may support IPv6parameter configuration via stateless DHCPv6.

The 5GC may support the allocation of a static IPv4 address and/or astatic IPv6 prefix based on subscription information in a UDM 140 and/orbased on the configuration on a per-subscriber, per-DNN basis.

User plane function(s) (UPF 110) may handle the user plane path of PDUsessions. A UPF 110 that provides the interface to a data network maysupport functionality of a PDU session anchor.

In an example, a policy control function, PCF 135, may support unifiedpolicy framework to govern network behavior, provide policy rules tocontrol plane function(s) to enforce policy rules, implement a front endto access subscription information relevant for policy decisions in auser data repository (UDR), and/or the like.

A network exposure function, NEF 125, may provide means to securelyexpose the services and capabilities provided by the 3GPP networkfunctions, translate between information exchanged with the AF 145 andinformation exchanged with the internal network functions, receiveinformation from other network functions, and/or the like.

In an example, an network repository function, NRF 130 may supportservice discovery function that may receive NF discovery request from NFinstance, provide information about the discovered NF instances (bediscovered) to the NF instance, and maintain information about availableNF instances and their supported services, and/or the like.

In an example, an NSSF 120 may select a set of network slice instancesserving the UE 100, may determine allowed NSSAI. In an example, the NSSF120 may determine the AMF 155 set to be employed to serve the UE 100,and/or, based on configuration, determine a list of candidate AMF 155(s)155 by querying the NRF 130.

In an example, stored data in a UDR may include at least usersubscription data, including at least subscription identifiers, securitycredentials, access and mobility related subscription data, sessionrelated subscription data, policy data, and/or the like.

In an example, an AUSF 150 may support authentication server function(AUSF 150).

In an example, an application function, AF 145, may interact with the3GPP core network to provide services. In an example, based on operatordeployment, application functions may be trusted by the operator tointeract directly with relevant network functions. Application functionsnot allowed by the operator to access directly the network functions mayuse an external exposure framework (e.g., via the NEF 125) to interactwith relevant network functions.

In an example, control plane interface between the (R)AN 105 and the 5Gcore may support connection of multiple different kinds of AN(s) (e.g.3GPP RAN 105, N3IWF 170 for Un-trusted access 165) to the 5GC via acontrol plane protocol. In an example, an N2 AP protocol may be employedfor both the 3GPP access 105 and non-3GPP access 165. In an example,control plane interface between the (R)AN 105 and the 5G core maysupport decoupling between AMF 155 and other functions such as SMF 160that may need to control the services supported by AN(s) (e.g. controlof the UP resources in the 105 for a PDU session).

In an example, the 5GC may provide policy information from the PCF 135to the UE 100. In an example, the policy information may comprise:access network discovery and selection policy, UE 100 route selectionpolicy (URSP), SSC mode selection policy (SSCMSP), network sliceselection policy (NSSP), DNN selection policy, non-seamless offloadpolicy, and/or the like.

In an example, as depicted in example FIG. 5A and FIG. 5B, theregistration management, RM may be employed to register or de-register aUE/user 100 with the network, and establish the user context in thenetwork. Connection management may be employed to establish and releasethe signaling connection between the UE 100 and the AMF 155.

In an example, a UE 100 may register with the network to receiveservices that require registration. In an example, the UE 100 may updateits registration with the network periodically in order to remainreachable (periodic registration update), or upon mobility (e.g.,mobility registration update), or to update its capabilities or tore-negotiate protocol parameters.

In an example, an initial registration procedure as depicted in exampleFIG. 8 and FIG. 9 may involve execution of network access controlfunctions (e.g. user authentication and access authorization based onsubscription profiles in UDM 140). Example FIG. 9 is a continuation ofthe initial registration procedure depicted in FIG. 8 . As a result ofthe initial registration procedure, the identity of the serving AMF 155may be registered in a UDM 140.

In an example, the registration management, RM procedures may beapplicable over both 3GPP access 105 and non 3GPP access 165.

An example FIG. 5A may depict the RM states of a UE 100 as observed bythe UE 100 and AMF 155. In an example embodiment, two RM states may beemployed in the UE 100 and the AMF 155 that may reflect the registrationstatus of the UE 100 in the selected PLMN: RM-DEREGISTERED 500, andRM-REGISTERED 510. In an example, in the RM DEREGISTERED state 500, theUE 100 may not be registered with the network. The UE 100 context in theAMF 155 may not hold valid location or routing information for the UE100 so the UE 100 may not be reachable by the AMF 155. In an example,the UE 100 context may be stored in the UE 100 and the AMF 155. In anexample, in the RM REGISTERED state 510, the UE 100 may be registeredwith the network. In the RM-REGISTERED 510 state, the UE 100 may receiveservices that may require registration with the network.

In an example embodiment, two RM states may be employed in AMF 155 forthe UE 100 that may reflect the registration status of the UE 100 in theselected PLMN: RM-DEREGISTERED 520, and RM-REGISTERED 530.

As depicted in example FIG. 6A and FIG. 6B, connection management, CM,may comprise establishing and releasing a signaling connection between aUE 100 and an AMF 155 over N1 interface. The signaling connection may beemployed to enable NAS signaling exchange between the UE 100 and thecore network. The signaling connection between the UE 100 and the AMF155 may comprise both the signaling connection between the UE 100 andthe (R)AN 105 (e.g. RRC connection over 3GPP access) and the N2connection for the UE 100 between the and the AMF 155.

As depicted in example FIG. 6A and FIG. 6B, two CM states may beemployed for the NAS signaling connectivity of the UE 100 with the AMF155, CM-IDLE 600, 620 and CM-CONNECTED 610, 630. A UE 100 in CM-IDLE 600state may be in RM-REGISTERED 510 state and may have no NAS signalingconnection established with the AMF 155 over N1. The UE 100 may performcell selection, cell reselection, PLMN selection, and/or the like. A UE100 in CM-CONNECTED 610 state may have a NAS signaling connection withthe AMF 155 over N1.

In an example embodiment two CM states may be employed for the UE 100 atthe AMF 155, CM-IDLE 620 and CM-CONNECTED 630.

In an example, an RRC inactive state may apply to NG-RAN (e.g. it mayapply to NR and E-UTRA connected to 5G CN). The AMF 155, based onnetwork configuration, may provide assistance information to the NG RAN105, to assist the NG RAN's 105 decision whether the UE 100 may be sentto RRC inactive state. When a UE 100 is CM-CONNECTED 610 with RRCinactive state, the UE 100 may resume the RRC connection due to uplinkdata pending, mobile initiated signaling procedure, as a response to RAN105 paging, to notify the network that it has left the RAN 105notification area, and/or the like.

In an example, a NAS signaling connection management may includeestablishing and releasing a NAS signaling connection. A NAS signalingconnection establishment function may be provided by the UE 100 and theAMF 155 to establish the NAS signaling connection for the UE 100 inCM-IDLE 600 state. The procedure of releasing the NAS signalingconnection may be initiated by the 5G (R)AN 105 node or the AMF 155.

In an example, reachability management of a UE 100 may detect whetherthe UE 100 is reachable and may provide the UE 100 location (e.g. accessnode) to the network to reach the UE 100. Reachability management may bedone by paging the UE 100 and the UE 100 location tracking. The UE 100location tracking may include both UE 100 registration area tracking andUE 100 reachability tracking. The UE 100 and the AMF 155 may negotiateUE 100 reachability characteristics in CM-IDLE 600, 620 state duringregistration and registration update procedures.

In an example, two UE 100 reachability categories may be negotiatedbetween a UE 100 and an AMF 155 for CM-IDLE 600, 620 state. 1) UE 100reachability allowing mobile device terminated data while the UE 100 isCM-IDLE 600 mode. 2) Mobile initiated connection only (MICO) mode. The5GC may support a PDU connectivity service that provides exchange ofPDUs between the UE 100 and a data network identified by a DNN. The PDUconnectivity service may be supported via PDU sessions that areestablished upon request from the UE 100.

In an example, a PDU session may support one or more PDU session types.PDU sessions may be established (e.g. upon UE 100 request), modified(e.g. upon UE 100 and 5GC request) and/or released (e.g. upon UE 100 and5GC request) using NAS SM signaling exchanged over N1 between the UE 100and the SMF 160. Upon request from an application server, the 5GC may beable to trigger a specific application in the UE 100. When receiving thetrigger, the UE 100 may send it to the identified application in the UE100. The identified application in the UE 100 may establish a PDUsession to a specific DNN.

In an example, the 5G QoS model may support a QoS flow based frameworkas depicted in example FIG. 7 . The 5G QoS model may support both QoSflows that require a guaranteed flow bit rate and QoS flows that may notrequire a guaranteed flow bit rate. In an example, the 5G QoS model maysupport reflective QoS. The QoS model may comprise flow mapping orpacket marking at the UPF 110 (CN_UP) 110, AN 105 and/or the UE 100. Inan example, packets may arrive from and/or destined to theapplication/service layer 730 of UE 100, UPF 110 (CN_UP) 110, and/or theAF 145.

In an example, the QoS flow may be a granularity of QoS differentiationin a PDU session. A QoS flow ID, QFI, may be employed to identify theQoS flow in the 5G system. In an example, user plane traffic with thesame QFI within a PDU session may receive the same traffic forwardingtreatment. The QFI may be carried in an encapsulation header on N3and/or N9 (e.g. without any changes to the end-to-end packet header). Inan example, the QFI may be applied to PDUs with different types ofpayload. The QFI may be unique within a PDU session.

In an example, the QoS parameters of a QoS flow may be provided to the(R)AN 105 as a QoS profile over N2 at PDU session establishment, QoSflow establishment, or when NG-RAN is used at every time the user planeis activated. In an example, a default QoS rule may be required forevery PDU session. The SMF 160 may allocate the QFI for a QoS flow andmay derive QoS parameters from the information provided by the PCF 135.In an example, the SMF 160 may provide the QFI together with the QoSprofile containing the QoS parameters of a QoS flow to the (R)AN 105.

In an example, 5G QoS flow may be a granularity for QoS forwardingtreatment in the 5G system. Traffic mapped to the same 5G QoS flow mayreceive the same forwarding treatment (e.g. scheduling policy, queuemanagement policy, rate shaping policy, RLC configuration, and/or thelike). In an example, providing different QoS forwarding treatment mayrequire separate 5G QoS flows.

In an example, a 5G QoS indicator may be a scalar that may be employedas a reference to a specific QoS forwarding behavior (e.g. packet lossrate, packet delay budget) to be provided to a 5G QoS flow. In anexample, the 5G QoS indicator may be implemented in the access networkby the 5QI referencing node specific parameters that may control the QoSforwarding treatment (e.g. scheduling weights, admission thresholds,queue management thresholds, link layer protocol configuration, and/orthe like.).

In an example, 5GC may support edge computing and may enable operator(s)and 3rd party services to be hosted close to the UE's access point ofattachment. The 5G core network may select a UPF 110 close to the UE 100and may execute the traffic steering from the UPF 110 to the local datanetwork via a N6 interface. In an example, the selection and trafficsteering may be based on the UE's 100 subscription data, UE 100location, the information from application function AF 145, policy,other related traffic rules, and/or the like. In an example, the 5G corenetwork may expose network information and capabilities to an edgecomputing application function. The functionality support for edgecomputing may include local routing where the 5G core network may selecta UPF 110 to route the user traffic to the local data network, trafficsteering where the 5G core network may select the traffic to be routedto the applications in the local data network, session and servicecontinuity to enable UE 100 and application mobility, user planeselection and reselection, e.g. based on input from applicationfunction, network capability exposure where 5G core network andapplication function may provide information to each other via NEf 125,QoS and charging where PCF 135 may provide rules for QoS control andcharging for the traffic routed to the local data network, support oflocal area data network where 5G core network may provide support toconnect to the LADN in a certain area where the applications aredeployed, and/or the like.

An example 5G system may be a 3GPP system comprising of 5G accessnetwork 105, 5G core network and a UE 100, and/or the like. AllowedNSSAI may be an NSSAI provided by a serving PLMN during e.g. aregistration procedure, indicating the NSSAI allowed by the network forthe UE 100 in the serving PLMN for the current registration area.

In an example, a PDU connectivity service may provide exchange of PDUsbetween a UE 100 and a data network. A PDU session may be an associationbetween the UE 100 and the data network, DN 115, that may provide thePDU connectivity service. The type of association may be IP, Ethernetand/or unstructured.

Establishment of user plane connectivity to a data network via networkslice instance(s) may comprise the following: performing a RM procedureto select an AMF 155 that supports the required network slices, andestablishing one or more PDU session(s) to the required data network viathe network slice instance(s).

In an example, the set of network slices for a UE 100 may be changed atany time while the UE 100 may be registered with the network, and may beinitiated by the network, or the UE 100.

In an example, a periodic registration update may be UE 100re-registration at expiry of a periodic registration timer. A requestedNSSAI may be a NSSAI that the UE 100 may provide to the network.

In an example, a service based interface may represent how a set ofservices may be provided/exposed by a given NF.

In an example, a service continuity may be an uninterrupted userexperience of a service, including the cases where the IP address and/oranchoring point may change. In an example, a session continuity mayrefer to continuity of a PDU session. For PDU session of IP type sessioncontinuity may imply that the IP address is preserved for the lifetimeof the PDU session. An uplink classifier may be a UPF 110 functionalitythat aims at diverting uplink traffic, based on filter rules provided bythe SMF 160, towards data network, DN 115.

In an example, the 5G system architecture may support data connectivityand services enabling deployments to use techniques such as e.g. networkfunction virtualization and/or software defined networking. The 5Gsystem architecture may leverage service-based interactions betweencontrol plane (CP) network functions where identified. In 5G systemarchitecture, separation of the user plane (UP) functions from thecontrol plane functions may be considered. A 5G system may enable anetwork function to interact with other NF(s) directly if required.

In an example, the 5G system may reduce dependencies between the accessnetwork (AN) and the core network (CN). The architecture may comprise aconverged access-agnostic core network with a common AN-CN interfacewhich may integrate different 3GPP and non-3GPP access types.

In an example, the 5G system may support a unified authenticationframework, stateless NFs, where the compute resource is decoupled fromthe storage resource, capability exposure, and concurrent access tolocal and centralized services. To support low latency services andaccess to local data networks, UP functions may be deployed close to theaccess network.

In an example, the 5G system may support roaming with home routedtraffic and/or local breakout traffic in the visited PLMN. An example 5Garchitecture may be service-based and the interaction between networkfunctions may be represented in two ways. (1) As service-basedrepresentation (depicted in example FIG. 1 ), where network functionswithin the control plane, may enable other authorized network functionsto access their services. This representation may also includepoint-to-point reference points where necessary. (2) Reference pointrepresentation, showing the interaction between the NF services in thenetwork functions described by point-to-point reference point (e.g. N11)between any two network functions.

In an example, a network slice may comprise the core network controlplane and user plane network functions, the 5G Radio Access Network; theN3IWF functions to the non-3GPP Access Network, and/or the like. Networkslices may differ for supported features and network functionimplementation. The operator may deploy multiple network slice instancesdelivering the same features but for different groups of UEs, e.g. asthey deliver a different committed service and/or because they may bededicated to a customer. The NSSF 120 may store the mapping informationbetween slice instance ID and NF ID (or NF address).

In an example, a UE 100 may simultaneously be served by one or morenetwork slice instances via a 5G-AN. In an example, the UE 100 may beserved by k network slices (e.g. k=8, 16, etc) at a time. An AMF 155instance serving the UE 100 logically may belong to a network sliceinstance serving the UE 100.

In an example, a PDU session may belong to one specific network sliceinstance per PLMN. In an example, different network slice instances maynot share a PDU session. Different slices may have slice-specific PDUsessions using the same DNN.

An S-NSSAI (Single Network Slice Selection Assistance information) mayidentify a network slice. An S-NSSAI may comprise a slice/service type(SST), which may refer to the expected network slice behavior in termsof features and services; and/or a slice differentiator (SD). A slicedifferentiator may be optional information that may complement theslice/service type(s) to allow further differentiation for selecting anetwork slice instance from potentially multiple network slice instancesthat comply with the indicated slice/service type. In an example, thesame network slice instance may be selected employing differentS-NSSAIs. The CN part of a network slice instance(s) serving a UE 100may be selected by CN.

In an example, subscription data may include the S-NSSAI(s) of thenetwork slices that the UE 100 subscribes to. One or more S-NSSAIs maybe marked as default S-NSSAI. In an example, k S-NSSAI may be markeddefault S-NSSAI (e.g. k=8, 16, etc.). In an example, the UE 100 maysubscribe to more than 8 S-NSSAIs.

In an example, a UE 100 may be configured by the HPLMN with a configuredNSSAI per PLMN. Upon successful completion of a UE's registrationprocedure, the UE 100 may obtain from the AMF 155 an Allowed NSSAI forthis PLMN, which may include one or more S-NSSAIs.

In an example, the Allowed NSSAI may take precedence over the configuredNSSAI for a PLMN. The UE 100 may use the S-NSSAIs in the allowed NSSAIcorresponding to a network slice for the subsequent network sliceselection related procedures in the serving PLMN.

In an example, the establishment of user plane connectivity to a datanetwork via a network slice instance(s) may comprise: performing a RMprocedure to select an AMF 155 that may support the required networkslices, establishing one or more PDU sessions to the required datanetwork via the network slice instance(s), and/or the like.

In an example, when a UE 100 registers with a PLMN, if the UE 100 forthe PLMN has a configured NSSAI or an allowed NSSAI, the UE 100 mayprovide to the network in RRC and NAS layer a requested NSSAI comprisingthe S-NSSAI(s) corresponding to the slice(s) to which the UE 100attempts to register, a temporary user ID if one was assigned to the UE,and/or the like. The requested NSSAI may be configured-NSSAI,allowed-NSSAI, and/or the like.

In an example, when a UE 100 registers with a PLMN, if for the PLMN theUE 100 has no configured NSSAI or allowed NSSAI, the RAN 105 may routeNAS signaling from/to the UE 100 to/from a default AMF 155.

In an example, the network, based on local policies, subscriptionchanges and/or UE 100 mobility, may change the set of permitted networkslice(s) to which the UE 100 is registered. In an example, the networkmay perform the change during a registration procedure or trigger anotification towards the UE 100 of the change of the supported networkslices using an RM procedure (which may trigger a registrationprocedure). The network may provide the UE 100 with a new allowed NSSAIand tracking area list.

In an example, during a registration procedure in a PLMN, in case thenetwork decides that the UE 100 should be served by a different AMF 155based on network slice(s) aspects, the AMF 155 that first received theregistration request may redirect the registration request to anotherAMF 155 via the RAN 105 or via direct signaling between the initial AMF155 and the target AMF 155.

In an example, the network operator may provision the UE 100 withnetwork slice selection policy (NSSP). The NSSP may comprise one or moreNSSP rules.

In an example, if a UE 100 has one or more PDU sessions establishedcorresponding to the a specific S-NSSAI, the UE 100 may route the userdata of the application in one of the PDU sessions, unless otherconditions in the UE 100 may prohibit the use of the PDU sessions. Ifthe application provides a DNN, then the UE 100 may consider the DNN todetermine which PDU session to use. In an example, if the UE 100 doesnot have a PDU session established with the specific S-NSSAI, the UE 100may request a new PDU session corresponding to the S-NSSAI and with theDNN that may be provided by the application. In an example, in order forthe RAN 105 to select a proper resource for supporting network slicingin the RAN 105, the RAN 105 may be aware of the network slices used bythe UE 100.

In an example, an AMF 155 may select an SMF 160 in a network sliceinstance based on S-NSSAI, DNN and/or other information e.g. UE 100subscription and local operator policies, and/or the like, when the UE100 triggers the establishment of a PDU session. The selected SMF 160may establish the PDU session based on S-NSSAI and DNN.

In an example, in order to support network-controlled privacy of sliceinformation for the slices the UE 100 may access, when the UE 100 isaware or configured that privacy considerations may apply to NSSAI, theUE 100 may not include NSSAI in NAS signaling unless the UE 100 has aNAS security context and the UE 100 may not include NSSAI in unprotectedRRC signaling.

In an example, for roaming scenarios, the network slice specific networkfunctions in VPLMN and HPLMN may be selected based on the S-NSSAIprovided by the UE 100 during PDU connection establishment. If astandardized S-NSSAI is used, selection of slice specific NF instancesmay be done by each PLMN based on the provided S-NSSAI. In an example,the VPLMN may map the S-NSSAI of HPLMN to a S-NSSAI of VPLMN based onroaming agreement (e.g., including mapping to a default S-NSSAI ofVPLMN). In an example, the selection of slice specific NF instance inVPLMN may be done based on the S-NSSAI of VPLMN. In an example, theselection of any slice specific NF instance in HPLMN may be based on theS-NSSAI of HPLMN.

As depicted in example FIG. 8 and FIG. 9 , a registration procedure maybe performed by the UE 100 to get authorized to receive services, toenable mobility tracking, to enable reachability, and/or the like.

In an example, the UE 100 may send to the (R)AN 105 an AN message 805(comprising AN parameters, RM-NAS registration request (registrationtype, SUCI or SUPI or 5G-GUTI, last visited TAI (if available), securityparameters, requested NSSAI, mapping of requested NSSAI, UE 100 5GCcapability, PDU session status, PDU session(s) to be re-activated,Follow on request, MICO mode preference, and/or the like), and/or thelike). In an example, in case of NG-RAN, the parameters may include e.g.SUCI or SUPI or the 5G-GUTI, the Selected PLMN ID and requested NSSAI,and/or the like. In an example, the parameters may compriseestablishment cause. The establishment cause may provide the reason forrequesting the establishment of an RRC connection. In an example, theregistration type may indicate if the UE 100 wants to perform an initialregistration (i.e. the UE 100 is in RM-DEREGISTERED state), a mobilityregistration update (e.g., the UE 100 is in RM-REGISTERED state andinitiates a registration procedure due to mobility), a periodicregistration update (e.g., the UE 100 is in RM-REGISTERED state and mayinitiate a registration procedure due to the periodic registrationupdate timer expiry) or an emergency registration (e.g., the UE 100 isin limited service state). In an example, if the UE 100 performing aninitial registration (i.e., the UE 100 is in RM-DEREGISTERED state) to aPLMN for which the UE 100 does not already have a 5G-GUTI, the UE 100may include its SUCI or SUPI in the registration request. The SUCI maybe included if the home network has provisioned the public key toprotect SUPI in the UE. If the UE 100 received a UE 100 configurationupdate command indicating that the UE 100 needs to re-register and the5G-GUTI is invalid, the UE 100 may perform an initial registration andmay include the SUPI in the registration request message. For anemergency registration, the SUPI may be included if the UE 100 does nothave a valid 5G-GUTI available; the PEI may be included when the UE 100has no SUPI and no valid 5G-GUTI. In other cases, the 5G-GUTI may beincluded and it may indicate the last serving AMF 155. If the UE 100 isalready registered via a non-3GPP access in a PLMN different from thenew PLMN (e.g., not the registered PLMN or an equivalent PLMN of theregistered PLMN) of the 3GPP access, the UE 100 may not provide over the3GPP access the 5G-GUTI allocated by the AMF 155 during the registrationprocedure over the non-3GPP access. If the UE 100 is already registeredvia a 3GPP access in a PLMN (e.g., the registered PLMN), different fromthe new PLMN (i.e. not the registered PLMN or an equivalent PLMN of theregistered PLMN) of the non-3GPP access, the UE 100 may not provide overthe non-3GPP access the 5G-GUTI allocated by the AMF 155 during theregistration procedure over the 3GPP access. The UE 100 may provide theUE's usage setting based on its configuration. In case of initialregistration or mobility registration update, the UE 100 may include themapping of requested NSSAI, which may be the mapping of each S-NSSAI ofthe requested NSSAI to the S-NSSAIs of the configured NSSAI for theHPLMN, to ensure that the network is able to verify whether theS-NSSAI(s) in the requested NSSAI are permitted based on the subscribedS-NSSAIs. If available, the last visited TAI may be included in order tohelp the AMF 155 produce registration area for the UE. In an example,the security parameters may be used for authentication and integrityprotection. requested NSSAI may indicate the network slice selectionassistance information. The PDU session status may indicates thepreviously established PDU sessions in the UE. When the UE 100 isconnected to the two AMF 155 belonging to different PLMN via 3GPP accessand non-3GPP access then the PDU session status may indicate theestablished PDU session of the current PLMN in the UE. The PDUsession(s) to be re-activated may be included to indicate the PDUsession(s) for which the UE 100 may intend to activate UP connections. APDU session corresponding to a LADN may not be included in the PDUsession(s) to be re-activated when the UE 100 is outside the area ofavailability of the LADN. The follow on request may be included when theUE 100 may have pending uplink signaling and the UE 100 may not includePDU session(s) to be re-activated, or the registration type may indicatethe UE 100 may want to perform an emergency registration.

In an example, if a SUPI is included or the 5G-GUTI does not indicate avalid AMF 155, the (R)AN 105, based on (R)AT and requested NSSAI, ifavailable, may selects 808 an AMF 155. If UE 100 is in CM-CONNECTEDstate, the (R)AN 105 may forward the registration request message to theAMF 155 based on the N2 connection of the UE. If the (R)AN 105 may notselect an appropriate AMF 155, it may forward the registration requestto an AMF 155 which has been configured, in (R)AN 105, to perform AMF155 selection 808.

In an example, the (R)AN 105 may send to the new AMF 155 an N2 message810 (comprising: N2 parameters, RM-NAS registration request(registration type, SUPI or 5G-GUTI, last visited TAI (if available),security parameters, requested NSSAI, mapping of requested NSSAI, UE 1005GC capability, PDU session status, PDU session(s) to be re-activated,follow on request, and MICO mode preference), and/or the like). In anexample, when NG-RAN is used, the N2 parameters may comprise theselected PLMN ID, location information, cell identity and the RAT typerelated to the cell in which the UE 100 is camping. In an example, whenNG-RAN is used, the N2 parameters may include the establishment cause.

In an example, the new AMF 155 may send to the old AMF 155 anNamf_Communication_UEContextTransfer (complete registration request)815. In an example, if the UE's 5G-GUTI was included in the registrationrequest and the serving AMF 155 has changed since last registrationprocedure, the new AMF 155 may invoke theNamf_Communication_UEContextTransfer service operation 815 on the oldAMF 155 including the complete registration request IE, which may beintegrity protected, to request the UE's SUPI and MM Context. The oldAMF 155 may use the integrity protected complete registration request IEto verify if the context transfer service operation invocationcorresponds to the UE 100 requested. In an example, the old AMF 155 maytransfer the event subscriptions information by each NF consumer, forthe UE, to the new AMF 155. In an example, if the UE 100 identifiesitself with PEI, the SUPI request may be skipped.

In an example, the old AMF 155 may send to new AMF 155 a response 815 toNamf_Communication_UEContextTransfer (SUPI, MM context, SMF 160information, PCF ID). In an example, the old AMF 155 may respond to thenew AMF 155 for the Namf_Communication_UEContextTransfer invocation byincluding the UE's SUPI and MM context. In an example, if old AMF 155holds information about established PDU sessions, the old AMF 155 mayinclude SMF 160 information including S-NSSAI(s), SMF 160 identities andPDU session ID. In an example, if old AMF 155 holds information aboutactive NGAP UE-TNLA bindings to N3IWF, the old AMF 155 may includeinformation about the NGAP UE-TNLA bindings.

In an example, if the SUPI is not provided by the UE 100 nor retrievedfrom the old AMF 155 the identity request procedure 820 may be initiatedby the AMF 155 sending an identity request message to the UE 100requesting the SUCI.

In an example, the UE 100 may respond with an identity response message820 including the SUCI. The UE 100 may derive the SUCI by using theprovisioned public key of the HPLMN.

In an example, the AMF 155 may decide to initiate UE 100 authentication825 by invoking an AUSF 150. The AMF 155 may select an AUSF 150 based onSUPI or SUCI. In an example, if the AMF 155 is configured to supportemergency registration for unauthenticated SUPIs and the UE 100indicated registration type emergency registration the AMF 155 may skipthe authentication and security setup or the AMF 155 may accept that theauthentication may fail and may continue the registration procedure.

In an example, the authentication 830 may be performed byNudm_UEAuthenticate_Get operation. The AUSF 150 may discover a UDM 140.In case the AMF 155 provided a SUCI to AUSF 150, the AUSF 150 may returnthe SUPI to AMF 155 after the authentication is successful. In anexample, if network slicing is used, the AMF 155 may decide if theregistration request needs to be rerouted where the initial AMF 155refers to the AMF 155. In an example, the AMF 155 may initiate NASsecurity functions. In an example, upon completion of NAS securityfunction setup, the AMF 155 may initiate NGAP procedure to enable 5G-ANuse it for securing procedures with the UE. In an example, the 5G-AN maystore the security context and may acknowledge to the AMF 155. The 5G-ANmay use the security context to protect the messages exchanged with theUE.

In an example, new AMF 155 may send to the old AMF 155Namf_Communication_RegistrationCompleteNotify 835. If the AMF 155 haschanged, the new AMF 155 may notify the old AMF 155 that theregistration of the UE 100 in the new AMF 155 may be completed byinvoking the Namf_Communication_RegistrationCompleteNotify serviceoperation. If the authentication/security procedure fails, then theregistration may be rejected, and the new AMF 155 may invoke theNamf_Communication_RegistrationCompleteNotify service operation with areject indication reason code towards the old AMF 155. The old AMF 155may continue as if the UE 100 context transfer service operation wasnever received. If one or more of the S-NSSAIs used in the oldregistration area may not be served in the target registration area, thenew AMF 155 may determine which PDU session may not be supported in thenew registration area. The new AMF 155 may invoke theNamf_Communication_RegistrationCompleteNotify service operationincluding the rejected PDU session ID and a reject cause (e.g. theS-NSSAI becomes no longer available) towards the old AMF 155. The newAMF 155 may modify the PDU session status correspondingly. The old AMF155 may inform the corresponding SMF 160(s) to locally release the UE'sSM context by invoking the Nsmf_PDUSession_ReleaseSMContext serviceoperation.

In an example, the new AMF 155 may send to the UE 100 an identityrequest/response 840 (e.g., PEI). If the PEI was not provided by the UE100 nor retrieved from the old AMF 155, the identity request proceduremay be initiated by AMF 155 sending an identity request message to theUE 100 to retrieve the PEI. The PEI may be transferred encrypted unlessthe UE 100 performs emergency registration and may not be authenticated.For an emergency registration, the UE 100 may have included the PEI inthe registration request.

In an example, the new AMF 155 may initiate ME identity check 845 byinvoking the N5g-eir_EquipmentIdentityCheck_Get service operation 845.

In an example, the new AMF 155, based on the SUPI, may select 905 a UDM140. The UDM 140 may select a UDR instance. In an example, the AMF 155may select a UDM 140.

In an example, if the AMF 155 has changed since the last registrationprocedure, or if the UE 100 provides a SUPI which may not refer to avalid context in the AMF 155, or if the UE 100 registers to the same AMF155 it has already registered to a non-3GPP access (e.g., the UE 100 isregistered over a non-3GPP access and may initiate the registrationprocedure to add a 3GPP access), the new AMF 155 may register with theUDM 140 using Nudm_UECM_Registration 910 and may subscribe to benotified when the UDM 140 may deregister the AMF 155. The UDM 140 maystore the AMF 155 identity associated to the access type and may notremove the AMF 155 identity associated to the other access type. The UDM140 may store information provided at registration in UDR, byNudr_UDM_Update. In an example, the AMF 155 may retrieve the access andmobility subscription data and SMF 160 selection subscription data usingNudm_SDM_Get 915. The UDM 140 may retrieve this information from UDR byNudr_UDM_Query (access and mobility subscription data). After asuccessful response is received, the AMF 155 may subscribe to benotified using Nudm_SDM_Subscribe 920 when the data requested may bemodified. The UDM 140 may subscribe to UDR by Nudr_UDM_Subscribe. TheGPSI may be provided to the AMF 155 in the subscription data from theUDM 140 if the GPSI is available in the UE 100 subscription data. In anexample, the new AMF 155 may provide the access type it serves for theUE 100 to the UDM 140 and the access type may be set to 3GPP access. TheUDM 140 may store the associated access type together with the servingAMF 155 in UDR by Nudr_UDM_Update. The new AMF 155 may create an MMcontext for the UE 100 after getting the mobility subscription data fromthe UDM 140. In an example, when the UDM 140 stores the associatedaccess type together with the serving AMF 155, the UDM 140 may initiatea Nudm_UECM_DeregistrationNotification 921 to the old AMF 155corresponding to 3GPP access. The old AMF 155 may remove the MM contextof the UE. If the serving NF removal reason indicated by the UDM 140 isinitial registration, then the old AMF 155 may invoke theNamf_EventExposure_Notify service operation towards all the associatedSMF 160 s of the UE 100 to notify that the UE 100 is deregistered fromold AMF 155. The SMF 160 may release the PDU session(s) on getting thisnotification. In an example, the old AMF 155 may unsubscribe with theUDM 140 for subscription data using Nudm_SDM_unsubscribe 922.

In an example, if the AMF 155 decides to initiate PCF 135 communication,e.g. the AMF 155 has not yet obtained access and mobility policy for theUE 100 or if the access and mobility policy in the AMF 155 are no longervalid, the AMF 155 may select 925 a PCF 135. If the new AMF 155 receivesa PCF ID from the old AMF 155 and successfully contacts the PCF 135identified by the PCF ID, the AMF 155 may select the (V-)PCF identifiedby the PCF ID. If the PCF 135 identified by the PCF ID may not be used(e.g. no response from the PCF 135) or if there is no PCF ID receivedfrom the old AMF 155, the AMF 155 may select 925 a PCF 135.

In an example, the new AMF 155 may perform a policy associationestablishment 930 during registration procedure. If the new AMF 155contacts the PCF 135 identified by the (V-)PCF ID received duringinter-AMF 155 mobility, the new AMF 155 may include the PCF-ID in theNpcf_AMPolicyControl Get operation. If the AMF 155 notifies the mobilityrestrictions (e.g. UE 100 location) to the PCF 135 for adjustment, or ifthe PCF 135 updates the mobility restrictions itself due to someconditions (e.g. application in use, time and date), the PCF 135 mayprovide the updated mobility restrictions to the AMF 155.

In an example, the PCF 135 may invoke Namf_EventExposure_Subscribeservice operation 935 for UE 100 event subscription.

In an example, the AMF 155 may send to the SMF 160 aNsmf_PDUSession_UpdateSMContext 936. In an example, the AMF 155 mayinvoke the Nsmf_PDUSession_UpdateSMContext if the PDU session(s) to bere-activated is included in the registration request. The AMF 155 maysend Nsmf_PDUSession_UpdateSMContext request to SMF 160(s) associatedwith the PDU session(s) to activate user plane connections of the PDUsession(s). The SMF 160 may decide to trigger e.g. the intermediate UPF110 insertion, removal or change of PSA. In the case that theintermediate UPF 110 insertion, removal, or relocation is performed forthe PDU session(s) not included in PDU session(s) to be re-activated,the procedure may be performed without N11 and N2 interactions to updatethe N3 user plane between (R)AN 105 and 5GC. The AMF 155 may invoke theNsmf_PDUSession_ReleaseSMContext service operation towards the SMF 160if any PDU session status indicates that it is released at the UE 100.The AMF 155 may invoke the Nsmf_PDUSession_ReleaseSMContext serviceoperation towards the SMF 160 in order to release any network resourcesrelated to the PDU session.

In an example, the new AMF 155155 may send to a N3IWF an N2 AMF 155mobility request 940. If the AMF 155 has changed, the new AMF 155 maycreate an NGAP UE 100 association towards the N3IWF to which the UE 100is connected. In an example, the N3IWF may respond to the new AMF 155with an N2 AMF 155 mobility response 940.

In an example, the new AMF 155 may send to the UE 100 a registrationaccept 955 (comprising: 5G-GUTI, registration area, mobilityrestrictions, PDU session status, allowed NSSAI, [mapping of allowedNSSAI], periodic registration update timer, LADN information andaccepted MICO mode, IMS voice over PS session supported indication,emergency service support indicator, and/or the like). In an example,the AMF 155 may send the registration accept message to the UE 100indicating that the registration request has been accepted. 5G-GUTI maybe included if the AMF 155 allocates a new 5G-GUTI. If the AMF 155allocates a new registration area, it may send the registration area tothe UE 100 via registration accept message 955. If there is noregistration area included in the registration accept message, the UE100 may consider the old registration area as valid. In an example,mobility restrictions may be included in case mobility restrictions mayapply for the UE 100 and registration type may not be emergencyregistration. The AMF 155 may indicate the established PDU sessions tothe UE 100 in the PDU session status. The UE 100 may remove locally anyinternal resources related to PDU sessions that are not marked asestablished in the received PDU session status. In an example, when theUE 100 is connected to the two AMF 155 belonging to different PLMN via3GPP access and non-3GPP access then the UE 100 may remove locally anyinternal resources related to the PDU session of the current PLMN thatare not marked as established in received PDU session status. If the PDUsession status information was in the registration request, the AMF 155may indicate the PDU session status to the UE. The mapping of allowedNSSAI may be the mapping of each S-NSSAI of the allowed NSSAI to theS-NSSAIs of the configured NSSAI for the HPLMN. The AMF 155 may includein the registration accept message 955 the LADN information for LADNsthat are available within the registration area determined by the AMF155 for the UE. If the UE 100 included MICO mode in the request, thenAMF 155 may respond whether MICO mode may be used. The AMF 155 may setthe IMS voice over PS session supported Indication. In an example, inorder to set the IMS voice over PS session supported indication, the AMF155 may perform a UE/RAN radio information and compatibility requestprocedure to check the compatibility of the UE 100 and RAN radiocapabilities related to IMS voice over PS. In an example, the emergencyservice support indicator may inform the UE 100 that emergency servicesare supported, e.g., the UE 100 may request PDU session for emergencyservices. In an example, the handover restriction list and UE-AMBR maybe provided to NG-RAN by the AMF 155.

In an example, the UE 100 may send to the new AMF 155 a registrationcomplete 960 message. In an example, the UE 100 may send theregistration complete message 960 to the AMF 155 to acknowledge that anew 5G-GUTI may be assigned. In an example, when information about thePDU session(s) to be re-activated is not included in the registrationrequest, the AMF 155 may release the signaling connection with the UE100. In an example, when the follow-on request is included in theregistration request, the AMF 155 may not release the signalingconnection after the completion of the registration procedure. In anexample, if the AMF 155 is aware that some signaling is pending in theAMF 155 or between the UE 100 and the 5GC, the AMF 155 may not releasethe signaling connection after the completion of the registrationprocedure.

As depicted in example FIG. 10 and FIG. 11 , a service request proceduree.g., a UE 100 triggered service request procedure may be used by a UE100 in CM-IDLE state to request the establishment of a secure connectionto an AMF 155. FIG. 11 is continuation of FIG. 10 depicting the servicerequest procedure. The service request procedure may be used to activatea user plane connection for an established PDU session. The servicerequest procedure may be triggered by the UE 100 or the 5GC, and may beused when the UE 100 is in CM-IDLE and/or in CM-CONNECTED and may allowselectively to activate user plane connections for some of theestablished PDU sessions.

In an example, a UE 100 in CM IDLE state may initiate the servicerequest procedure to send uplink signaling messages, user data, and/orthe like, as a response to a network paging request, and/or the like. Inan example, after receiving the service request message, the AMF 155 mayperform authentication. In an example, after the establishment ofsignaling connection to the AMF 155, the UE 100 or network may sendsignaling messages, e.g. PDU session establishment from the UE 100 to aSMF 160, via the AMF 155.

In an example, for any service request, the AMF 155 may respond with aservice accept message to synchronize PDU session status between the UE100 and network. The AMF 155 may respond with a service reject messageto the UE 100, if the service request may not be accepted by thenetwork. The service reject message may include an indication or causecode requesting the UE 100 to perform a registration update procedure.In an example, for service request due to user data, network may takefurther actions if user plane connection activation may not besuccessful. In an example FIG. 10 and FIG. 11 , more than one UPF, e.g.,old UPF 110-2 and PDU session Anchor PSA UPF 110-3 may be involved.

In an example, the UE 100 may send to a (R)AN 105 an AN messagecomprising AN parameters, mobility management, MM NAS service request1005 (e.g., list of PDU sessions to be activated, list of allowed PDUsessions, security parameters, PDU session status, and/or the like),and/or the like. In an example, the UE 100 may provide the list of PDUsessions to be activated when the UE 100 may re-activate the PDUsession(s). The list of allowed PDU sessions may be provided by the UE100 when the service request may be a response of a paging or a NASnotification, and may identify the PDU sessions that may be transferredor associated to the access on which the service request may be sent. Inan example, for the case of NG-RAN, the parameters may include selectedPLMN ID, and an establishment cause. The establishment cause may providethe reason for requesting the establishment of an RRC connection. The UE100 may send NAS service request message towards the AMF 155encapsulated in an RRC message to the RAN 105.

In an example, if the service request may be triggered for user data,the UE 100 may identify, using the list of PDU sessions to be activated,the PDU session(s) for which the UP connections are to be activated inthe NAS service request message. If the service request may be triggeredfor signaling, the UE 100 may not identify any PDU session(s). If thisprocedure may be triggered for paging response, and/or the UE 100 mayhave at the same time user data to be transferred, the UE 100 mayidentify the PDU session(s) whose UP connections may be activated in MMNAS service request message, by the list of PDU sessions to beactivated.

In an example, if the service request over 3GPP access may be triggeredin response to a paging indicating non-3GPP access, the NAS servicerequest message may identify in the list of allowed PDU sessions thelist of PDU sessions associated with the non-3GPP access that may bere-activated over 3GPP. In an example, the PDU session status mayindicate the PDU sessions available in the UE 100. In an example, the UE100 may not trigger the service request procedure for a PDU sessioncorresponding to a LADN when the UE 100 may be outside the area ofavailability of the LADN. The UE 100 may not identify such PDUsession(s) in the list of PDU sessions to be activated, if the servicerequest may be triggered for other reasons.

In an example, the (R)AN 105 may send to AMF 155 an N2 Message 1010(e.g., a service request) comprising N2 parameters, MM NAS servicerequest, and/or the like. The AMF 155 may reject the N2 message if itmay not be able to handle the service request. In an example, if NG-RANmay be used, the N2 parameters may include the 5G-GUTI, selected PLMNID, location information, RAT type, establishment cause, and/or thelike. In an example, the 5G-GUTI may be obtained in RRC procedure andthe (R)AN 105 may select the AMF 155 according to the 5G-GUTI. In anexample, the location information and RAT type may relate to the cell inwhich the UE 100 may be camping. In an example, based on the PDU sessionstatus, the AMF 155 may initiate PDU session release procedure in thenetwork for the PDU sessions whose PDU session ID(s) may be indicated bythe UE 100 as not available.

In an example, if the service request was not sent integrity protectedor integrity protection verification failed, the AMF 155 may initiate aNAS authentication/security procedure 1015.

In an example, if the UE 100 triggers the service request to establish asignaling connection, upon successful establishment of the signalingconnection, the UE 100 and the network may exchange NAS signaling.

In an example the AMF 155 may send to the SMF 160 a PDU session updatecontext request 1020 e.g., Nsmf_PDUSession_UpdateSMContext requestcomprising PDU session ID(s), Cause(s), UE 100 location information,access type, and/or the like.

In an example, the Nsmf_PDUSession_UpdateSMContext request may beinvoked by the AMF 155 if the UE 100 may identify PDU session(s) to beactivated in the NAS service request message. In an example, theNsmf_PDUSession_UpdateSMContext request may be triggered by the SMF 160wherein the PDU session(s) identified by the UE 100 may correlate toother PDU session ID(s) than the one triggering the procedure. In anexample, the Nsmf_PDUSession_UpdateSMContext request may be triggered bythe SMF 160 wherein the current UE 100 location may be outside the areaof validity for the N2 information provided by the SMF 160 during anetwork triggered service request procedure. The AMF 155 may not sendthe N2 information provided by the SMF 160 during the network triggeredservice request procedure.

In an example, the AMF 155 may determine the PDU session(s) to beactivated and may send an Nsmf_PDUSession_UpdateSMContext request to SMF160(s) associated with the PDU session(s) with cause set to indicateestablishment of user plane resources for the PDU session(s).

In an example, if the procedure may be triggered in response to pagingindicating non-3GPP access, and the list of allowed PDU sessionsprovided by the UE 100 may not include the PDU session for which the UE100 was paged, the AMF 155 may notify the SMF 160 that the user planefor the PDU session may not be re-activated. The service requestprocedure may succeed without re-activating the user plane of any PDUsessions, and the AMF 155 may notify the UE 100.

In an example, if the PDU session ID may correspond to a LADN and theSMF 160 may determine that the UE 100 may be outside the area ofavailability of the LADN based on the UE 100 location reporting from theAMF 155, the SMF 160 may decide to (based on local policies) keep thePDU session, may reject the activation of user plane connection for thePDU session and may inform the AMF 155. In an example, if the proceduremay be triggered by a network triggered service request, the SMF 160 maynotify the UPF 110 that originated the data notification to discarddownlink data for the PDU sessions and/or to not provide further datanotification messages. The SMF 160 may respond to the AMF 155 with anappropriate reject cause and the user plane activation of PDU sessionmay be stopped.

In an example, if the PDU session ID may correspond to a LADN and theSMF 160 may determine that the UE 100 may be outside the area ofavailability of the LADN based on the UE 100 location reporting from theAMF 155, the SMF 160 may decide to (based on local policies) release thePDU session. The SMF 160 may locally release the PDU session and mayinform the AMF 155 that the PDU session may be released. The SMF 160 mayrespond to the AMF 155 with an appropriate reject cause and the userplane Activation of PDU session may be stopped.

In an example, if the UP activation of the PDU session may be acceptedby the SMF 160, based on the location info received from the AMF 155,the SMF 160 may check the UPF 110 Selection 1025 Criteria (e.g., sliceisolation requirements, slice coexistence requirements, UPF's 110dynamic load, UPF's 110 relative static capacity among UPFs supportingthe same DNN, UPF 110 location available at the SMF 160, UE 100 locationinformation, Capability of the UPF 110 and the functionality requiredfor the particular UE 100 session. In an example, an appropriate UPF 110may be selected by matching the functionality and features required fora UE 100, DNN, PDU session type (i.e. IPv4, IPv6, ethernet type orunstructured type) and if applicable, the static IP address/prefix, SSCmode selected for the PDU session, UE 100 subscription profile in UDM140, DNAI as included in the PCC rules, local operator policies,S-NSSAI, access technology being used by the UE 100, UPF 110 logicaltopology, and/or the like), and may determine to perform one or more ofthe following: continue using the current UPF(s); may select a newintermediate UPF 110 (or add/remove an intermediate UPF 110), if the UE100 has moved out of the service area of the UPF 110 that was previouslyconnecting to the (R)AN 105, while maintaining the UPF(s) acting as PDUsession anchor; may trigger re-establishment of the PDU session toperform relocation/reallocation of the UPF 110 acting as PDU sessionanchor, e.g. the UE 100 has moved out of the service area of thechor UPF110 which is connecting to RAN 105.

In an example, the SMF 160 may send to the UPF 110 (e.g., newintermediate UPF 110) an N4 session establishment request 1030. In anexample, if the SMF 160 may select a new UPF 110 to act as intermediateUPF 110-2 for the PDU session, or if the SMF 160 may select to insert anintermediate UPF 110 for a PDU session which may not have anintermediate UPF 110-2, an N4 session establishment request 1030 messagemay be sent to the new UPF 110, providing packet detection, dataforwarding, enforcement and reporting rules to be installed on the newintermediate UPF. The PDU session anchor addressing information (on N9)for this PDU session may be provided to the intermediate UPF 110-2.

In an example, if a new UPF 110 is selected by the SMF 160 to replacethe old (intermediate) UPF 110-2, the SMF 160 may include a dataforwarding indication. The data forwarding indication may indicate tothe UPF 110 that a second tunnel endpoint may be reserved for bufferedDL data from the old I-UPF.

In an example, the new UPF 110 (intermediate) may send to SMF 160 an N4session establishment response message 1030. In case the UPF 110 mayallocate CN tunnel info, the UPF 110 may provide DL CN tunnel info forthe UPF 110 acting as PDU session anchor and UL CN tunnel info (e.g., CNN3 tunnel info) to the SMF 160. If the data forwarding indication may bereceived, the new (intermediate) UPF 110 acting as N3 terminating pointmay send DL CN tunnel info for the old (intermediate) UPF 110-2 to theSMF 160. The SMF 160 may start a timer, to release the resource in theold intermediate UPF 110-2.

In an example, if the SMF 160 may selects a new intermediate UPF 110 forthe PDU session or may remove the old I-UPF 110-2, the SMF 160 may sendN4 session modification request message 1035 to PDU session anchor, PSAUPF 110-3, providing the data forwarding indication and DL tunnelinformation from new intermediate UPF 110.

In an example, if the new intermediate UPF 110 may be added for the PDUsession, the (PSA) UPF 110-3 may begin to send the DL data to the newI-UPF 110 as indicated in the DL tunnel information.

In an example, if the service request may be triggered by the network,and the SMF 160 may remove the old I-UPF 110-2 and may not replace theold I-UPF 110-2 with the new I-UPF 110, the SMF 160 may include the dataforwarding indication in the request. The data forwarding indication mayindicate to the (PSA) UPF 110-3 that a second tunnel endpoint may bereserved for buffered DL data from the old I-UPF 110-2. In this case,the PSA UPF 110-3 may begin to buffer the DL data it may receive at thesame time from the N6 interface.

In an example, the PSA UPF 110-3 (PSA) may send to the SMF 160 an N4session modification response 1035. In an example, if the dataforwarding indication may be received, the PSA UPF 110-3 may become asN3 terminating point and may send CN DL tunnel info for the old(intermediate) UPF 110-2 to the SMF 160. The SMF 160 may start a timer,to release the resource in old intermediate UPF 110-2 if there is one.

In an example, the SMF 160 may send to the old UPF 110-2 an N4 sessionmodification request 1045 (e.g., may comprise new UPF 110 address, newUPF 110 DL tunnel ID, and/or the like). In an example, if the servicerequest may be triggered by the network, and/or the SMF 160 may removethe old (intermediate) UPF 110-2, the SMF 160 may send the N4 sessionmodification request message to the old (intermediate) UPF 110-2, andmay provide the DL tunnel information for the buffered DL data. If theSMF 160 may allocate new I-UPF 110, the DL tunnel information is fromthe new (intermediate) UPF 110 may act as N3 terminating point. If theSMF 160 may not allocate a new I-UPF 110, the DL tunnel information maybe from the new UPF 110 (PSA) 110-3 acting as N3 terminating point. TheSMF 160 may start a timer to monitor the forwarding tunnel. In anexample, the old (intermediate) UPF 110-2 may send N4 sessionmodification response message to the SMF 160.

In an example, if the I-UPF 110-2 may be relocated and forwarding tunnelwas established to the new I-UPF 110, the old (intermediate) UPF 110-2may forward its buffered data to the new (intermediate) UPF 110 actingas N3 terminating point. In an example, if the old I-UPF 110-2 may beremoved and the new I-UPF 110 may not be assigned for the PDU sessionand forwarding tunnel may be established to the UPF 110 (PSA) 110-3, theold (intermediate) UPF 110-2 may forward its buffered data to the UPF110 (PSA) 110-3 acting as N3 terminating point.

In an example, the SMF 160 may send to the AMF 155 an N11 message 1060e.g., a Nsmf_PDUSession_UpdateSMContext response (comprising: N1 SMcontainer (PDU session ID, PDU session re-establishment indication), N2SM information (PDU session ID, QoS profile, CN N3 tunnel info,S-NSSAI), Cause), upon reception of the Nsmf_PDUSession_UpdateSMContextrequest with a cause including e.g., establishment of user planeresources. The SMF 160 may determine whether UPF 110 reallocation may beperformed, based on the UE 100 location information, UPF 110 servicearea and operator policies. In an example, for a PDU session that theSMF 160 may determine to be served by the current UPF 110, e.g., PDUsession anchor or intermediate UPF, the SMF 160 may generate N2 SMinformation and may send an Nsmf_PDUSession_UpdateSMContext response1060 to the AMF 155 to establish the user plane(s). The N2 SMinformation may contain information that the AMF 155 may provide to theRAN 105. In an example, for a PDU session that the SMF 160 may determineas requiring a UPF 110 relocation for PDU session anchor UPF, the SMF160 may reject the activation of UP of the PDU session by sendingNsmf_PDUSession_UpdateSMContext response that may contain N1 SMcontainer to the UE 100 via the AMF 155. The N1 SM container may includethe corresponding PDU session ID and PDU session re-establishmentindication.

Upon reception of the Namf_EventExposure_Notify from the AMF 155 to theSMF 160, with an indication that the UE 100 is reachable, if the SMF 160may have pending DL data, the SMF 160 may invoke theNamf_Communication_N1N2MessageTransfer service operation to the AMF 155to establish the user plane(s) for the PDU sessions. In an example, theSMF 160 may resume sending DL data notifications to the AMF 155 in caseof DL data.

In an example, the SMF 160 may send a message to the AMF 155 to rejectthe activation of UP of the PDU session by including a cause in theNsmf_PDUSession_UpdateSMContext response if the PDU session maycorrespond to a LADN and the UE 100 may be outside the area ofavailability of the LADN, or if the AMF 155 may notify the SMF 160 thatthe UE 100 may be reachable for regulatory prioritized service, and thePDU session to be activated may not for a regulatory prioritizedservice; or if the SMF 160 may decide to perform PSA UPF 110-3relocation for the requested PDU session.

In an example, the AMF 155 may send to the (R)AN 105 an N2 requestmessage 1065 (e.g., N2 SM information received from SMF 160, securitycontext, AMF 155 signaling connection ID, handover restriction list, MMNAS service accept, list of recommended cells/TAs/NG-RAN nodeidentifiers). In an example, the RAN 105 may store the security context,AMF 155 signaling connection Id, QoS information for the QoS flows ofthe PDU sessions that may be activated and N3 tunnel IDs in the UE 100RAN 105 context. In an example, the MM NAS service accept may includePDU session status in the AMF 155. If the activation of UP of a PDUsession may be rejected by the SMF 160, the MM NAS service accept mayinclude the PDU session ID and the reason why the user plane resourcesmay not be activated (e.g. LADN not available). Local PDU sessionrelease during the session request procedure may be indicated to the UE100 via the session Status.

In an example, if there are multiple PDU sessions that may involvemultiple SMF 160 s, the AMF 155 may not wait for responses from all SMF160 s before it may send N2 SM information to the UE 100. The AMF 155may wait for all responses from the SMF 160 s before it may send MM NASservice accept message to the UE 100.

In an example, the AMF 155 may include at least one N2 SM informationfrom the SMF 160 if the procedure may be triggered for PDU session userplane activation. AMF 155 may send additional N2 SM information from SMF160 s in separate N2 message(s) (e.g. N2 tunnel setup request), if thereis any. Alternatively, if multiple SMF 160 s may be involved, the AMF155 may send one N2 request message to (R)AN 105 after all theNsmf_PDUSession_UpdateSMContext response service operations from all theSMF 160 s associated with the UE 100 may be received. In such case, theN2 request message may include the N2 SM information received in each ofthe Nsmf_PDUSession_UpdateSMContext response and PDU session ID toenable AMF 155 to associate responses to relevant SMF 160.

In an example, if the RAN 105 (e.g., NG RAN) node may provide the listof recommended cells/TAs/NG-RAN node identifiers during the releaseprocedure, the AMF 155 may include the information from the list in theN2 request. The RAN 105 may use this information to allocate the RAN 105notification area when the RAN 105 may decide to enable RRC inactivestate for the UE 100.

If the AMF 155 may receive an indication, from the SMF 160 during a PDUsession establishment procedure that the UE 100 may be using a PDUsession related to latency sensitive services, for any of the PDUsessions established for the UE 100 and the AMF 155 has received anindication from the UE 100 that may support the CM-CONNECTED with RRCinactive state, then the AMF 155 may include the UE's RRC inactiveassistance information. In an example, the AMF 155 based on networkconfiguration, may include the UE's RRC inactive assistance information.

In an example, the (R)AN 105 may send to the UE 100 a message to performRRC connection reconfiguration 1070 with the UE 100 depending on the QoSinformation for all the QoS flows of the PDU sessions whose UPconnections may be activated and data radio bearers. In an example, theuser plane security may be established.

In an example, if the N2 request may include a MM NAS service acceptmessage, the RAN 105 may forward the MM NAS service accept to the UE100. The UE 100 may locally delete context of PDU sessions that may notbe available in 5GC.

In an example, if the N1 SM information may be transmitted to the UE 100and may indicate that some PDU session(s) may be re-established, the UE100 may initiate PDU session re-establishment for the PDU session(s)that me be re-established after the service request procedure may becomplete.

In an example, after the user plane radio resources may be setup, theuplink data from the UE 100 may be forwarded to the RAN 105. The RAN 105(e.g., NG-RAN) may send the uplink data to the UPF 110 address andtunnel ID provided.

In an example, the (R)AN 105 may send to the AMF 155 an N2 request Ack1105 (e.g., N2 SM information (comprising: AN tunnel info, list ofaccepted QoS flows for the PDU sessions whose UP connections areactivated, list of rejected QoS flows for the PDU sessions whose UPconnections are activated)). In an example, the N2 request message mayinclude N2 SM information(s), e.g. AN tunnel info. RAN 105 may respondN2 SM information with separate N2 message (e.g. N2 tunnel setupresponse). In an example, if multiple N2 SM information are included inthe N2 request message, the N2 request Ack may include multiple N2 SMinformation and information to enable the AMF 155 to associate theresponses to relevant SMF 160.

In an example, the AMF 155 may send to the SMF 160 aNsmf_PDUSession_UpdateSMContext request 1110 (N2 SM information (ANtunnel info), RAT type) per PDU session. If the AMF 155 may receive N2SM information (one or multiple) from the RAN 105, then the AMF 155 mayforward the N2 SM information to the relevant SMF 160. If the UE 100time zone may change compared to the last reported UE 100 Time Zone thenthe AMF 155 may include the UE 100 time zone IE in theNsmf_PDUSession_UpdateSMContext request message.

In an example, if dynamic PCC is deployed, the SMF 160 may initiatenotification about new location information to the PCF 135 (ifsubscribed) by invoking an event exposure notification operation (e.g.,a Nsmf_EventExposure_Notify service operation). The PCF 135 may provideupdated policies by invoking a policy control update notificationmessage 1115 (e.g., a Npcf_SMPolicyControl_UpdateNotify operation).

In an example, if the SMF 160 may select a new UPF 110 to act asintermediate UPF 110 for the PDU session, the SMF 160 may initiates anN4 session modification procedure 1120 to the new I-UPF 110 and mayprovide AN tunnel info. The downlink data from the new I-UPF 110 may beforwarded to RAN 105 and UE 100. In an example, the UPF 110 may send tothe SMF 160, an N4 session modification response 1120. In an example,the SMF 160 may send to the AMF 155, an Nsmf_PDUSession_UpdateSMContextresponse 1140.

In an example, if forwarding tunnel may be established to the new I-UPF110 and if the timer SMF 160 set for forwarding tunnel may be expired,the SMF 160 may sends N4 session modification request 1145 to new(intermediate) UPF 110 acting as N3 terminating point to release theforwarding tunnel. In an example, the new (intermediate) UPF 110 maysend to the SMF 160 an N4 session modification response 1145. In anexample, the SMF 160 may send to the PSA UPF 110-3 an N4 sessionmodification request 1150, or N4 session release request. In an example,if the SMF 160 may continue using the old UPF 110-2, the SMF 160 maysend an N4 session modification request 1155, providing AN tunnel info.In an example, if the SMF 160 may select a new UPF 110 to act asintermediate UPF 110, and the old UPF 110-2 may not be PSA UPF 110-3,the SMF 160 may initiate resource release, after timer expires, bysending an N4 session release request (release cause) to the oldintermediate UPF 110-2.

In an example, the old intermediate UPF 110-2 may send to the SMF 160 anN4 session modification response or N4 session release response 1155.The old UPF 110-2 may acknowledge with the N4 session modificationresponse or N4 session release response message to confirm themodification or release of resources. The AMF 155 may invoke theNamf_EventExposure_Notify service operation to notify the mobilityrelated events, after this procedure may complete, towards the NFs thatmay have subscribed for the events. In an example, the AMF 155 mayinvoke the Namf_EventExposure_Notify towards the SMF 160 if the SMF 160had subscribed for UE 100 moving into or out of area of interest and ifthe UE's current location may indicate that it may be moving into ormoving outside of the area of interest subscribed, or if the SMF 160 hadsubscribed for LADN DNN and if the UE 100 may be moving into or outsideof an area where the LADN is available, or if the UE 100 may be in MICOmode and the AMF 155 had notified an SMF 160 of the UE 100 beingunreachable and that SMF 160 may not send DL data notifications to theAMF 155, and the AMF 155 may informs the SMF 160 that the UE 100 isreachable, or if the SMF 160 had subscribed for UE 100 reachabilitystatus, then the AMF 155 may notify the UE 100 reachability.

An example PDU session establishment procedure depicted in FIG. 12 andFIG. 13 . In an example embodiment, when the PDU session establishmentprocedure may be employed, the UE 100 may send to the AMF 155 a NASMessage 1205 (or a SM NAS message) comprising NSSAI, S-NSSAI (e.g.,requested S-NSSAI, allowed S-NSSAI, subscribed S-NSSAI, and/or thelike), DNN, PDU session ID, request type, old PDU session ID, N1 SMcontainer (PDU session establishment request), and/or the like. In anexample, the UE 100, in order to establish a new PDU session, maygenerate a new PDU session ID. In an example, when emergency service maybe required and an emergency PDU session may not already be established,the UE 100 may initiate the UE 100 requested PDU session establishmentprocedure with a request type indicating emergency request. In anexample, the UE 100 may initiate the UE 100 requested PDU sessionestablishment procedure by the transmission of the NAS messagecontaining a PDU session establishment request within the N1 SMcontainer. The PDU session establishment request may include a PDU type,SSC mode, protocol configuration options, and/or the like. In anexample, the request type may indicate initial request if the PDUsession establishment is a request to establish the new PDU session andmay indicate existing PDU session if the request refers to an existingPDU session between 3GPP access and non-3GPP access or to an existingPDN connection in EPC. In an example, the request type may indicateemergency request if the PDU session establishment may be a request toestablish a PDU session for emergency services. The request type mayindicate existing emergency PDU session if the request refers to anexisting PDU session for emergency services between 3GPP access andnon-3GPP access. In an example, the NAS message sent by the UE 100 maybe encapsulated by the in a N2 message towards the AMF 155 that mayinclude user location information and access technology typeinformation. In an example, the PDU session establishment requestmessage may contain SM PDU DN request container containing informationfor the PDU session authorization by the external DN. In an example, ifthe procedure may be triggered for SSC mode 3 operation, the UE 100 mayinclude the old PDU session ID which may indicate the PDU session ID ofthe on-going PDU session to be released, in the NAS message. The old PDUsession ID may be an optional parameter which may be included in thiscase. In an example, the AMF 155 may receive from the NAS message (e.g.,NAS SM message) together with user location information (e.g. cell ID incase of the RAN 105). In an example, the UE 100 may not trigger a PDUsession establishment for a PDU session corresponding to a LADN when theUE 100 is outside the area of availability of the LADN.

In an example, the AMF 155 may determine that the NAS message or the SMNAS message may correspond to the request for the new PDU session basedon that request type indicates initial request and that the PDU sessionID may not be used for any existing PDU session(s) of the UE 100. If theNAS message does not contain an S-NSSAI, the AMF 155 may determine adefault S-NSSAI for the requested PDU session either according to the UE100 subscription, if it may contain only one default S-NSSAI, or basedon operator policy. In an example, the AMF 155 may perform SMF 160selection 1210 and select an SMF 160. If the request type may indicateinitial request or the request may be due to handover from EPS, the AMF155 may store an association of the S-NSSAI, the PDU session ID and aSMF 160 ID. In an example, if the request type is initial request and ifthe old PDU session ID indicating the existing PDU session may becontained in the message, the AMF 155 may select the SMF 160 and maystore an association of the new PDU session ID and the selected SMF 160ID.

In an example, the AMF 155 may send to the SMF 160, an N11 message 1215,e.g., Nsmf_PDUSession_CreateSMContext request (comprising: SUPI or PEI,DNN, S-NSSAI, PDU session ID, AMF 155 ID, request type, N1 SM container(PDU session establishment request), user location information, accesstype, PEI, GPSI), or Nsmf_PDUSession_UpdateSMContext request (SUPI, DNN,S-NSSAI, PDU session ID, AMF 155 ID, request type, N1 SM container (PDUsession establishment request), user location information, access type,RAT type, PEI). In an example, if the AMF 155 may not have anassociation with the SMF 160 for the PDU session ID provided by the UE100 (e.g when request type indicates initial request), the AMF 155 mayinvoke the Nsmf_PDUSession_CreateSMContext request, but if the AMF 155already has an association with an SMF 160 for the PDU session IDprovided by the UE 100 (e.g when request type indicates existing PDUsession), the AMF 155 may invoke the Nsmf_PDUSession_UpdateSMContextrequest. In an example, the AMF 155 ID may be the UE's GUAMI whichuniquely identifies the AMF 155 serving the UE 100. The AMF 155 mayforward the PDU session ID together with the N1 SM container containingthe PDU session establishment request received from the UE 100. The AMF155 may provide the PEI instead of the SUPI when the UE 100 hasregistered for emergency services without providing the SUPI. In casethe UE 100 has registered for emergency services but has not beenauthenticated, the AMF 155 may indicate that the SUPI has not beenauthenticated.

In an example, if the request type may indicate neither emergencyrequest nor existing emergency PDU session and, if the SMF 160 has notyet registered and subscription data may not be available, the SMF 160may register with the UDM 140, and may retrieve subscription data 1225and subscribes to be notified when subscription data may be modified. Inan example, if the request type may indicate existing PDU session orexisting emergency PDU session, the SMF 160 may determine that therequest may be due to handover between 3GPP access and non-3GPP accessor due to handover from EPS. The SMF 160 may identify the existing PDUsession based on the PDU session ID. The SMF 160 may not create a new SMcontext but instead may update the existing SM context and may providethe representation of the updated SM context to the AMF 155 in theresponse. if the request type may be initial request and if the old PDUsession ID may be included in Nsmf_PDUSession_CreateSMContext request,the SMF 160 may identify the existing PDU session to be released basedon the old PDU session ID.

In an example, the SMF 160 may send to the AMF 155, the N11 messageresponse 1220, e.g., either a PDU session create/update response,Nsmf_PDUSession_CreateSMContext response 1220 (cause, SM context ID orN1 SM container (PDU session reject(cause))) or anNsmf_PDUSession_UpdateSMContext response.

In an example, if the SMF 160 may perform secondaryauthorization/authentication 1230 during the establishment of the PDUsession by a DN-AAA server, the SMF 160 may select a UPF 110 and maytrigger a PDU session establishment authentication/authorization.

In an example, if the request type may indicate initial request, the SMF160 may select an SSC mode for the PDU session. The SMF 160 may selectone or more UPFs as needed. In case of PDU type IPv4 or IPv6, the SMF160 may allocate an IP address/prefix for the PDU session. In case ofPDU type IPv6, the SMF 160 may allocate an interface identifier to theUE 100 for the UE 100 to build its link-local address. For UnstructuredPDU type the SMF 160 may allocate an IPv6 prefix for the PDU session andN6 point-to-point tunneling (based on UDP/IPv6).

In an example, if dynamic PCC is deployed, the may SMF 160 performs PCF135 selection 1235. If the request type indicates existing PDU sessionor existing emergency PDU session, the SMF 160 may use the PCF 135already selected for the PDU session. If dynamic PCC is not deployed,the SMF 160 may apply local policy.

In an example, the SMF 160 may perform a session management policyestablishment procedure 1240 to establish a PDU session with the PCF 135and may get the default PCC Rules for the PDU session. The GPSI may beincluded if available at the SMF 160. If the request type in 1215indicates existing PDU session, the SMF 160 may notify an eventpreviously subscribed by the PCF 135 by a session management policymodification procedure and the PCF 135 may update policy information inthe SMF 160. The PCF 135 may provide authorized session-AMBR and theauthorized 5QI and ARP to SMF 160. The PCF 135 may subscribe to the IPallocation/release event in the SMF 160 (and may subscribe otherevents).

In an example, the PCF 135, based on the emergency DNN, may set the ARPof the PCC rules to a value that may be reserved for emergency services.

In an example, if the request type in 1215 indicates initial request,the SMF 160 may select an SSC mode for the PDU session. The SMF 160 mayselect 1245 one or more UPFs as needed. In case of PDU type IPv4 orIPv6, the SMF 160 may allocate an IP address/prefix for the PDU session.In case of PDU type IPv6, the SMF 160 may allocate an interfaceidentifier to the UE 100 for the UE 100 to build its link-local address.For unstructured PDU type the SMF 160 may allocate an IPv6 prefix forthe PDU session and N6 point-to-point tunneling (e.g., based onUDP/IPv6). In an example, for Ethernet PDU type PDU session, neither aMAC nor an IP address may be allocated by the SMF 160 to the UE 100 forthis PDU session.

In an example, if the request type in 1215 is existing PDU session, theSMF 160 may maintain the same IP address/prefix that may be allocated tothe UE 100 in the source network.

In an example, if the request type in 1215 indicates existing PDUsession referring to an existing PDU session moved between 3GPP accessand non-3GPP access, the SMF 160 may maintain the SSC mode of the PDUsession, e.g., the current PDU session Anchor and IP address. In anexample, the SMF 160 may trigger e.g. new intermediate UPF 110 insertionor allocation of a new UPF 110. In an example, if the request typeindicates emergency request, the SMF 160 may select 1245 the UPF 110 andmay select SSC mode 1.

In an example, the SMF 160 may perform a session management policymodification 1250 procedure to report some event to the PCF 135 that haspreviously subscribed. If request type is initial request and dynamicPCC is deployed and PDU type is IPv4 or IPv6, the SMF 160 may notify thePCF 135 (that has previously subscribed) with the allocated UE 100 IPaddress/prefix.

In an example, the PCF 135 may provide updated policies to the SMF 160.The PCF 135 may provide authorized session-AMBR and the authorized 5QIand ARP to the SMF 160.

In an example, if request type indicates initial request, the SMF 160may initiate an N4 session establishment procedure 1255 with theselected UPF 110. The SMF 160 may initiate an N4 session modificationprocedure with the selected UPF 110. In an example, the SMF 160 may sendan N4 session establishment/modification request 1255 to the UPF 110 andmay provide packet detection, enforcement, reporting rules, and/or thelike to be installed on the UPF 110 for this PDU session. If CN tunnelinfo is allocated by the SMF 160, the CN tunnel info may be provided tothe UPF 110. If the selective user plane deactivation is required forthis PDU session, the SMF 160 may determine the Inactivity Timer and mayprovide it to the UPF 110. In an example, the UPF 110 may acknowledgesby sending an N4 session establishment/modification response 1255. If CNtunnel info is allocated by the UPF, the CN tunnel info may be providedto SMF 160. In an example, if multiple UPFs are selected for the PDUsession, the SMF 160 may initiate N4 session establishment/modificationprocedure 1255 with each UPF 110 of the PDU session.

In an example, the SMF 160 may send to the AMF 155 anNamf_Communication_N1N2MessageTransfer 1305 message (comprising PDUsession ID, access type, N2 SM information (PDU session ID, QFI(s), QoSprofile(s), CN tunnel info, S-NSSAI, session-AMBR, PDU session type,and/or the like), N1 SM container (PDU session establishment accept (QoSRule(s), selected SSC mode, S-NSSAI, allocated IPv4 address, interfaceidentifier, session-AMBR, selected PDU session type, and/or the like))).In case of multiple UPFs are used for the PDU session, the CN tunnelinfo may comprise tunnel information related with the UPF 110 thatterminates N3. In an example, the N2 SM information may carryinformation that the AMF 155 may forward to the (R)AN 105 (e.g., the CNtunnel info corresponding to the core network address of the N3 tunnelcorresponding to the PDU session, one or multiple QoS profiles and thecorresponding QFIs may be provided to the (R)AN 105, the PDU session IDmay be used by AN signaling with the UE 100 to indicate to the UE 100the association between AN resources and a PDU session for the UE100,and/or the like). In an example, a PDU session may be associated to anS-NSSAI and a DNN. In an example, the N1 SM container may contain thePDU session establishment accept that the AMF 155 may provide to the UE100. In an example, multiple QoS rules and QoS profiles may be includedin the PDU session establishment accept within the N1 SM and in the N2SM information. In an example, theNamf_Communication_N1N2MessageTransfer 1305 may further comprise the PDUsession ID and information allowing the AMF 155 to know which accesstowards the UE 100 to use.

In an example, the AMF 155 may send to the (R)AN105 an N2 PDU sessionrequest 1310 (comprising N2 SM information, NAS message (PDU session ID,N1 SM container (PDU session establishment accept, and/or the like))).In an example, the AMF 155 may send the NAS message 1310 that maycomprise PDU session ID and PDU session establishment accept targeted tothe UE 100 and the N2 SM information received from the SMF 160 withinthe N2 PDU session request 1310 to the (R)AN 105.

In an example, the (R)AN 105 may issue AN specific signaling exchange1315 with the UE 100 that may be related with the information receivedfrom SMF 160. In an example, in case of a 3GPP RAN 105, an RRCconnection reconfiguration procedure may take place with the UE 100 toestablish the necessary RAN 105 resources related to the QoS Rules forthe PDU session request 1310. In an example, (R)AN 105 may allocate(R)AN 105 N3 tunnel information for the PDU session. In case of dualconnectivity, the master RAN 105 node may assign some (zero or more)QFIs to be setup to a master RAN 105 node and others to the secondaryRAN 105 node. The tunnel info may comprise a tunnel endpoint for eachinvolved RAN 105 node, and the QFIs assigned to each tunnel endpoint. AQFI may be assigned to either the master RAN 105 node or the secondaryRAN 105 node. In an example, (R)AN 105 may forward the NAS message 1310(PDU session ID, N1 SM container (PDU session establishment accept)) tothe UE 100. The (R)AN 105 may provide the NAS message to the UE 100 ifthe necessary RAN 105 resources are established and the allocation of(R)AN 105 tunnel information are successful.

In an example, the N2 PDU session response 1320 may comprise a PDUsession ID, cause, N2 SM information (PDU session ID, AN tunnel info,list of accepted/rejected QFI(s)), and/or the like. In an example, thetunnel info may correspond to the access network address of the N3tunnel corresponding to the PDU session.

In an example, the AMF 155 may forward the N2 SM information receivedfrom (R)AN 105 to the SMF 160 via a Nsmf_PDUSession_UpdateSMContextrequest 1330 (comprising: N2 SM information, request type, and/or thelike). In an example, if the list of rejected QFI(s) is included in N2SM information, the SMF 160 may release the rejected QFI(s) associatedQoS profiles.

In an example, the SMF 160 may initiate an N4 session modificationprocedure 1335 with the UPF110. The SMF 160 may provide AN tunnel infoto the UPF 110 as well as the corresponding forwarding rules. In anexample, the UPF 110 may provide an N4 session modification response1335 to the SMF 160160.

In an example, the SMF 160 may send to the AMF 155 anNsmf_PDUSession_UpdateSMContext response 1340 (Cause). In an example,the SMF 160 may subscribe to the UE 100 mobility event notification fromthe AMF 155 (e.g. location reporting, UE 100 moving into or out of areaof interest), after this step by invoking Namf_EventExposure Subscribeservice operation. For LADN, the SMF 160 may subscribe to the UE 100moving into or out of LADN service area event notification by providingthe LADN DNN as an indicator for the area of interest. The AMF 155 mayforward relevant events subscribed by the SMF 160.

In an example, the SMF 160 may send to the AMF 155, aNsmf_PDUSession_SMContextStatusNotify (release) 1345. In an example, ifduring the procedure, any time the PDU session establishment is notsuccessful, the SMF 160 may inform the AMF 155 by invokingNsmf_PDUSession_SMContextStatusNotify(release) 1345. The SMF 160 mayreleases any N4 session(s) created, any PDU session address if allocated(e.g IP address) and may release the association with the PCF 135.

In an example, in case of PDU type IPv6, the SMF 160 may generate anIPv6 Router Advertisement 1350 and may send it to the UE 100 via N4 andthe UPF 110.

In an example, if the PDU session may not be established, the SMF 160may unsubscribe 1360 to the modifications of session managementsubscription data for the corresponding (SUPI, DNN, S-NSSAI), usingNudm_SDM_Unsubscribe (SUPI, DNN, S-NSSAI), if the SMF 160 is no morehandling a PDU session of the UE 100 for this (DNN, S-NSSAI). In anexample, if the PDU session may not be established, the SMF 160 mayderegister 1360 for the given PDU session using Nudm_UECM_Deregistration(SUPI, DNN, PDU session ID).

FIG. 14 illustrates another example of a mobile communication network inwhich embodiments of the present disclosure may be implemented. Themobile communication network depicted in FIG. 14 includes a wirelessdevice 1410, a base station 1420, a physical core network deployment ofone or more network functions 1430 (henceforth “CN deployment 1430”),and a physical core network deployment of one or more network functions1440 (henceforth “CN deployment 1440”). The deployment 1430 and thedeployment 1440 may be elements of a core network.

The wireless device 1410 may communicate with the base station 1420 overan air interface 1470. The communication direction from the wirelessdevice 1410 to the base station 1420 over the air interface is known asuplink, and the communication direction from the base station 1420 tothe wireless device 1410 over the air interface 1470 is known asdownlink. Downlink transmissions may be separated from uplinktransmissions using FDD, TDD, and/or some combination of the twoduplexing techniques. FIG. 14 shows a single wireless device 1410 and asingle base station 1420, but it will be understood that the wirelessdevice 1410 may communicate with any number of base stations or otheraccess network components over the air interface 1470, and that the basestation 1420 may communicate with any number of wireless devices overthe air interface 1470.

The wireless device 1410 may comprise a processing system 1411 and amemory 1412. The memory 1412 may comprise one or more computer-readablemedia, for example, one or more non-transitory computer readable media.The memory 1412 may include instructions 1413. The processing system1411 may process and/or execute the instructions 1413. Processing and/orexecution of the instructions 1413 may cause the processing system 1411to perform one or more functions or activities. The memory 1412 mayinclude data (not shown). One of the functions or activities performedby the processing system 1411 may be to store data in the memory 1412and/or retrieve previously-stored data from the memory 1412. In anexample, downlink data received from the base station 1420 may be storedin the memory 1412, and uplink data for transmission to the base station1420 may be retrieved from the memory 1412. The wireless device 1410 maycommunicate with the base station 1420 using a transmission processingsystem 1414 and a reception processing system 1415. The wireless device1410 may comprise one or more antennas 1416 to access the air interface1470. Although not shown in FIG. 14 , the transmission processing system1414 and/or the reception processing system 1415 may be coupled to adedicated memory that is analogous to but separate from the memory 1412,and comprises instructions that may be processed and/or executed tocarry out one or more of their respective functionalities.

The wireless device 1410 may comprise one or more other elements 1419.The one or more other elements 1419 may comprise software and/orhardware that provide features and/or functionalities, for example, aspeaker, a microphone, a keypad, a display, a touchpad, a satellitetransceiver, a universal serial bus (USB) port, a hands-free headset, afrequency modulated (FM) radio unit, a media player, an Internetbrowser, an electronic control unit (e.g., for a motor vehicle), and/orone or more sensors (e.g., an accelerometer, a gyroscope, a temperaturesensor, a radar sensor, a lidar sensor, an ultrasonic sensor, a lightsensor, a camera, a global positioning sensor (GPS) and/or the like).The wireless device 1410 may receive user input data from and/or provideuser output data to the one or more one or more other elements 1419. Theone or more other elements 1419 may comprise a power source. Thewireless device 1410 may receive power from the power source and may beconfigured to distribute the power to the other components in thewireless device 1410. The power source may comprise one or more sourcesof power, for example, a battery, a solar cell, a fuel cell, or anycombination thereof.

The wireless device 1410 may transmit data to the base station 1420 viathe air interface 1470. To perform the transmission, the processingsystem 1411 may implement layer 3 and layer 2 open systemsinterconnection (OSI) functionality to process the data for uplinktransmission. Layer 3 may include a radio resource control layer (RRC).Layer 14 may include a service data application protocol layer (SDAP), apacket data convergence protocol layer (PDCP), a radio link controllayer (RLC), and a media access control layer (MAC). The data may beprovided to the transmission processing system 1414, which may implementlayer 1 OSI functionality. Layer 1 may include a physical layer (PHY).The wireless device 1410 may transmit the data over the air interface1470 using one or more antennas 1416. For scenarios where the one ormore antennas 1416 include multiple antennas, the multiple antennas maybe used to perform one or more multi-antenna techniques, such as spatialmultiplexing (e.g., single-user multiple-input multiple output (MIMO) ormulti-user MIMO), transmit/receive diversity, and/or beamforming.

The wireless device 1410 may receive downlink data from the base station1420 over the air interface 1470. The downlink data may be received viathe one or more antennas 1416. The reception processing system 1415 mayimplement layer 1 OSI functionality on the received downlink data andmay provide the data to the processing system 1411. The processingsystem 1411 may implement layer 2 and layer 3 OSI functionality toprocess the received downlink data. The base station 1420 may compriseelements analogous to the elements of the wireless device 1410. The basestation 1420 may comprise a processing system 1421 and a memory 1422.The memory 1422 may comprise one or more computer-readable media, forexample, one or more non-transitory computer readable media. The memory1422 may include instructions 1423. The processing system 1421 mayprocess and/or execute the instructions 1423. Processing and/orexecution of the instructions 1423 may cause the processing system 1421to perform one or more functions or activities. The memory 1422 mayinclude data (not shown). One of the functions or activities performedby the processing system 1421 may be to store data in the memory 1422and/or retrieve previously-stored data from the memory 1422. The basestation 1420 may communicate with the wireless device 1410 using atransmission processing system 1424 and a reception processing system1425. The base station 1420 may comprise one or more antennas 1426 toaccess the air interface 1470. The processing system 1421 may implementlayer 14 and layer 3 OSI functionality. The transmission processingsystem 1424 and the reception processing system 1425 may implement layer1 OSI functionality to perform transmission of downlink data andreception of uplink data, respectively.

The base station 1420 may comprise an interface system 1427. Theinterface system 1427 may communicate with one or more elements of thecore network via an interface 1480. The interface 1480 may be wiredand/or wireless and the interface system 1427 may include one or morecomponents suitable for communicating via the interface 1480. In FIG. 14, the interface 1480 connects the base station 1420 to a single CNdeployment 1430, but it will be understood that the wireless device 1410may communicate with any number of CN deployments over the interface1480, and that the CN deployment 1430 may communicate with any number ofbase stations over the interface 1480. The base station 1420 maycomprise one or more other elements 1429 analogous to one or more of theone or more other elements 1419.

The CN deployment 1430 may comprise one or more network functions (NFs).For example, the CN deployment 1430 may comprise an AMF and/or a UPFanalogous to the AMF and UPF depicted in FIG. 1 . The CN deployment 1430may comprise elements analogous to the elements of the wireless device1410 and the base station 1420, as described above. The CN deployment1430 may comprise a processing system 1431 and a memory 1432. The memory1432 may comprise one or more computer-readable media, for example, oneor more non-transitory computer readable media. The memory 1432 mayinclude instructions 1433. The processing system 1431 may process and/orexecute the instructions 1433. Processing and/or execution of theinstructions 1433 may cause the processing system 1431 to perform one ormore functions or activities. The memory 1432 may include data (notshown). One of the functions or activities performed by the processingsystem 1431 may be to store data in the memory 1432 and/or retrievepreviously-stored data from the memory 1432. The CN deployment 1430 mayaccess the interface 1480 using an interface system 1437. The CNdeployment 1430 may also use the interface system 1437 to access aninterface 1490. The CN deployment 1430 may use the interface 1490 tocommunicate with one or more data networks (analogous to, for example,the DN(s) depicted in FIG. 1 and/or one or more other CN deployments,including the CN deployment 1440 depicted in FIG. 14 . The CN deployment1430 may comprise one or more other elements 1439.

The CN deployment 1440 may comprise elements analogous to the elementsof the CN deployment 1430, as described above. The CN deployment 1440may comprise a processing system 1441 and a memory 1442. The memory 1442may comprise one or more computer-readable media, for example, one ormore non-transitory computer readable media. The memory 1442 may includeinstructions 1443. The processing system 1441 may process and/or executethe instructions 1443. Processing and/or execution of the instructions1443 may cause the processing system 1441 to perform one or morefunctions or activities. The memory 1442 may include data (not shown).One of the functions or activities performed by the processing system1441 may be to store data in the memory 1442 and/or retrievepreviously-stored data from the memory 1442. The CN deployment 1440 mayaccess the interface 1490 using an interface system 1447. The CNdeployment 1440 may comprise one or more other elements.

The processing system 1411, the processing system 1421, the processingsystem 1431, and/or the processing system 1441 may comprise one or morecontrollers and/or one or more processors. The one or more controllersand/or one or more processors may comprise, for example, ageneral-purpose processor, a digital signal processor (DSP), amicrocontroller, an application specific integrated circuit (ASIC), afield programmable gate array (FPGA) and/or other programmable logicdevice, discrete gate and/or transistor logic, discrete hardwarecomponents, an on-board unit, or any combination thereof. The processingsystem 1411, the processing system 1421, the processing system 1431,and/or the processing system 1441 may perform signal coding/processing,data processing, power control, input/output processing, and/or anyother functionality that may enable the wireless device 1410, basestation 1420, CN deployment 1430, and/or CN deployment 1440 to operatein a mobile communications system.

Each CN deployment may comprise one or more network functions. Dependingon the context in which the term is used, a network function (NF) mayrefer to a particular set of functionalities and/or one or more physicalelements configured to perform those functionalities (e.g., a processingsystem and memory comprising instructions that, when executed by theprocessing system, cause the processing system to perform thefunctionalities). There are many different types of NF and each type ofNF may be associated with a different set of functionalities. DifferentNFs may be flexibly deployed at different locations (for example, indifferent physical core network deployments) or in a same location (forexample, co-located in the same physical core network deployment).Moreover, physical CN deployment are not limited to implementation ofNFs. For example, a particular physical CN deployment may furtherinclude a base station or portions therefor and/or a data network orportions thereof. Accordingly, one or more NFs implemented on aparticular physical core network deployment may be co-located with oneor more non-core elements, including elements of an access network ordata network.

In an example, FIG. 15 is a diagram of 5G policy and charging controlsystem architecture. The reference architecture of policy and chargingcontrol framework for the 5G system may comprise one or more of thefollowing network functions: policy control function (PCF), sessionmanagement function (SMF), user plane function (UPF), access andmobility management function (AMF), network exposure functionality(NEF), network data analytics function (NWDAF), charging function (CHF),application function (AF) and unified data repository (UDR).

In an example, the CHF may support at least one charging method: offlinecharging, online charging, or converged charging. In an example, theoffline charging may be a process where charging information for networkresource usage may be collected concurrently with that resource usage.At the end of the process, CDR files may be generated by the network,which may be transferred to a network operator's billing domain (BD) forthe purpose of subscriber billing and/or inter-operator accounting (oradditional functions, e.g. statistics, at the operator's discretion).The BD typically comprises post-processing systems such as theoperator's billing system or billing mediation device. In an exampleconclusion, offline charging may be a mechanism where charginginformation does not affect, in real-time, the service rendered. In anexample, online charging may be a process where charging information fornetwork resource usage may be collected concurrently with that resourceusage in the same fashion as in offline charging. However, authorizationfor the network resource usage may be obtained by the network prior tothe actual resource usage to occur. In an example, the charginginformation utilized in online charging may be not necessarily identicalto the charging information employed in offline charging. In an exampleconclusion, online charging may be a mechanism where charginginformation may affect, in real-time, the service rendered and thereforea direct interaction of the charging mechanism with the control ofnetwork resource usage may be required. In an example, convergedcharging may be a process where online and offline charging may becombined.

FIG. 16 is an example call flow for PDU session establishment chargingas per an aspect of an embodiment of the present disclosure. In anexample, a UE may initiate a PDU Session establishment procedure. A PDUSession Establishment Request may comprise one or more of: PDU SessionID, PDU Type, SSC mode, User location information and Access TechnologyType Information. In response to the message received from the UE, anAMF may select an SMF and send to the selected SMF a message (e.g.Namf_PDUSession_CreateSMContext Request). The SMF may send to the AMF aresponse message (e.g. Namf_PDUSession_CreateSMContext Response).

In an example, the SMF may select a PCF and send to the PCF a message(e.g. SM Policy Association Establishment Request) to request PCC rules,and the PCF may provide PCC rules in a response message (e.g. SM PolicyAssociation Establishment response). In an example, the SMF may create aCharging Id for the PDU session and may send a Charging Data Request[initial] message to a CHF for authorization for the subscriber to startthe PDU session which is triggered by start of PDU session chargingevent. In an example, the CHF may open CDR for this PDU session and mayacknowledge by sending a Charging Data Response [Initial] to the SMF. Inan example, the SMF select a UPF and may initiate an N4 SessionEstablishment/Modification procedure with the selected UPF. The SMF mayinteract with the AMF, in an example, the SMF may send to the AMF aNamf_Communication_N1N2MessageTransfer message comprising one or moreof: PDU Session ID, QoS Profile(s), CN Tunnel Info, and S-NSSAI from theAllowed NSSAI. In an example, the AMF may interact with (R)AN and UE bysending to the (R)AN a N2 PDU Session Request message comprising theinformation received from the SMF, indicating the PDU sessionestablishment is accepted.

In an example, the (R)AN may send to the AMF a N2 PDU Session Responsemessage comprising one or more of: PDU Session ID, N2 SM information(PDU Session ID, AN Tunnel Info, List of accepted/rejected QFI(s)),wherein the Tunnel Info may be corresponding to the Access Networkaddress of the N3 tunnel corresponding to the PDU Session. In anexample, the AMF may send to the SMF a Nsmf_PDUSession_UpdateSMContextRequest message comprising the N2 SM information received from (R)AN tothe SMF. In an example, the SMF may initiate an N4 Session Modificationprocedure with the UPF. The SMF may provide AN Tunnel Info to the UPF aswell as the corresponding forwarding rules. The UPF may send to the SMFa response message. In an example, the SMF may request quota from CHF,e.g. “start of service data flow” event may need quota from CHF. The SMFmay send a message to the CHF (e.g. Charging Data Request [update]). Asan example, for online charging or converged charging, the SMF mayrequest quota from CHF when allocated quota is consumed or a trigger ismet to request a quota.

In an example, the UPF may report resource usage of a PDU session to theSMF. As an example, the UPF may report resource usage of a wirelessdevice to the SMF. by enforcing the charging control rules, the SMF maysend to the CHF a message (e.g. Charging Data Request [update])comprising resource usage information received from the UPF. In anexample, the CHF may update CDR for this PDU session. The CHF mayacknowledge the SMF by sending a Charging Data Response message. In anexample, the SMF may send to the AMF a Nsmf_PDUSession_UpdateSMContextResponse message.

FIG. 17 is a diagram of a first example arrangement of a local locationmanagement component (LMC) associated with a base station as per anaspect of an embodiment of the present disclosure. In an examplearchitecture, the LMC may be an internal function of the NG-RAN node. Incase of split gNB, the LMC may be located in the gNB-CU-CP. Theinterface between the LMC and the serving NG-RAN node may be internal,and therefore may minimize the latency between the LMC and servingNG-RAN node. Functions of the NLs interface (e.g. an NL1 interfacebetween an AMF and LMF) could be specified also for the NG-C interface.The characteristics of this example architecture may be that no newinterface is needed. The characteristics of this example architecturemay be that positioning-related signalling is internal to the gNB whenUE positioning involves only transmission and reception points (TRPs)within the NG-RAN node. The characteristics of this example architecturemay be that to support location continuity in case of handover, LMCrelocation to the target NG-RAN node may be enabled via enhancements tothe XnAP Handover Preparation procedure.

FIG. 18 is a diagram of a second example arrangement of an LMCassociated with a base station as per an aspect of an embodiment of thepresent disclosure. In an example architecture, the LMC may be a logicalnode within the split gNB connected to the gNB-CU-CP via a newinterface. This example architecture may require a dedicated interfacebetween the LMC and the serving NG-RAN node. The impacts to the NG-Cinterface may be the same as the example architecture in FIG. 17 . Thecharacteristics of this example architecture may be that new interfacebetween the LMC and the gNB-CU-CP is needed. The characteristics of thisexample architecture may be that LMC and gNB-CU-CP may be provided bydifferent vendors. The characteristics of this example architecture maybe that offloading of positioning support from a gNB-CU is allowed.

FIG. 19 is a diagram of a third example arrangement of an LMC associatedwith a base station as per an aspect of an embodiment of the presentdisclosure. In an example architecture, the LMC may be a new logicalnode outside or inside a NG-RAN, connected to NG-RAN nodes (gNBs and/orng-eNBs) via a new interface. This example architecture may require adedicated interface between the LMC and the serving NG-RAN node. Theimpacts to the NG-C interface may be the same as the examplearchitecture in FIG. 17 and may be supported by the new interface. Thecharacteristics of this example architecture may be that new interfacebetween the LMC and the NG-RAN node is needed. The characteristics ofthis example architecture may be that LMC and NG-RAN nodes may beprovided by different vendors. The characteristics of this examplearchitecture may be that a single LMC may support multiple NG-RAN nodes(i.e. avoid introducing LMC in each individual NG-RAN node). Thecharacteristics of this example architecture may be that offloading ofpositioning support from a gNB-CU is allowed. The characteristics ofthis example architecture may be that to support location continuity incase of handover when both source and target NG-RAN nodes are served bythe same LMC, LMC relocation may not be needed.

FIG. 20 is a diagram of an example architecture for location service asper an aspect of an embodiment of the present disclosure. In an example,an access network may be involved in the handling of various positioningprocedures including positioning of a target UE, provision of locationrelated information not associated with a particular target UE andtransfer of positioning messages between an AMF or LMF and a target UE.In an example, AFs and NFs may access LCS services from a GMLC in thesame trust domain (e.g. in the same PLMN) using the Ngmlc interface orEvent Exposure with location information from an AMF in the same trustdomain using the Namf interface. LCS clients may access LCS servicesfrom a GMLC (e.g. HGMLC) using the Le reference point. External AFs mayaccess LCS services from a NEF using Nnef interface. A Gateway MobileLocation Centre (GMLC) may contain functionality required to supportLCS. In one PLMN, there may be more than one GMLC. A GMLC is the firstnode an external LCS client accesses in a PLMN (i.e. the Le referencepoint is supported by the GMLC). AFs and NFs may access GMLC directly orvia NEF. The GMLC may request routing information and/or target UEprivacy information from a UDM via the Nudm interface. After performingauthorization of an external LCS Client or AF and verifying target UEprivacy, a GMLC may forward a location request to either a serving AMFusing Namf interface or to a GMLC in another PLMN using the Ngmlcinterface in the case of a roaming UE. A location retrieval function(LRF) may be collocated with a GMLC or separate. The LRF is responsiblefor retrieving or validating location information, providing routingand/or correlation information for a UE which has initiated an IMSemergency session. The information may be provided by an LRF to anE-CSCF.

In an example, a UE may support positioning with four different modes. AUE may support positioning with UE assisted mode, where the UE mayperform location measurements and send the measurements to anotherentity (e.g. an LMF) to compute a location. A UE may support positioningwith UE based mode, where the UE may perform location measurements andcomputes a location estimate making use of assistance data provided byserving PLMN. A UE may support positioning with standalone mode, wherethe UE may perform location measurements and compute a location estimatewithout making use of assistance data provided by serving PLMN. A UE maysupport positioning with network based mode, where a serving PLMN mayperform location measurements of signals transmitted by a target UE andcompute a location estimate.

In an example, the transmission of UE signals for network based mode mayor may not be transparent to the UE. A limited set of UE positioningcapability information may be transferred to the 5GCN duringregistration of the UE. Some of this positioning capability informationmay be transferred subsequently to an LMF. UE positioning capabilityinformation may also be transferred directly to a location server (e.g.LMF). A UE may support additional functions to support locationservices. For example, a UE may support location requests received froma network for 5GC-MT-LR, 5GC-NI-LR or a deferred 5GC-MT-LR for periodicor triggered location. For example, a UE may support location requeststo a network for a 5GC-MO-LR. For example, a UE may support privacynotification and verification for a 5GC-MT-LR or deferred 5GC-MT-LR forperiodic or triggered location. For example, a UE may support sendingupdated privacy requirements to a serving AMF (for transfer to a UDR viaUDM). For example, a UE may support periodic or triggered locationreporting to an LMF. For example, a UE may support change of a servingLMF for periodic or triggered location reporting. For example, a UE maysupport cancelation of periodic or triggered location reporting. Forexample, a UE may support multiple simultaneous location sessions. Forexample, a UE may support reception of unciphered and/or cipheredassistance data broadcast by NG-RAN. For example, a UE may supportreception of ciphering keys for the assistance data from the AMF.

In an example, an AMF may contain functionality responsible for managingpositioning for a target UE for all types of location request. The AMFmay be accessible to the GMLC and NEF via the Namf interface, to the RANvia the N2 reference point and to the UE via the N1 reference point. TheAMF may perform one or more functions to support location services. Forexample, the AMF may initiate an NI-LR location request for a UE with anIMS emergency call. For example, the AMF may receive and manage locationrequests from a GMLC for a 5GC-MT-LR and deferred 5GC-MT-LR forperiodic, triggered and UE available location events. For example, theAMF may receive and manage location requests from a UE for a 5GC-MO-LR.For example, the AMF may receive and manage event exposure request forlocation information from an NEF. For example, the AMF may select anLMF, optionally taking into account UE access type(s), serving AN node,network slicing, QoS, LCS Client type, RAN configuration information,LMF capabilities, LMF load. LMF location, indication of either a singleevent report or multiple event reports, duration of event reporting. Forexample, the AMF may receive updated privacy requirements from a UE andtransfer to a UDR via UDM. For example, the AMF may support cancelationof periodic or triggered location reporting for a target UE. Forexample, the AMF may support change of a serving LMF for periodic ortriggered location reporting for a target UE. For example, whenassistance data is broadcast by 5GS in ciphered form, the AMF mayreceive ciphering keys from the LMF and forwards to suitably subscribedUEs using mobility management procedures.

In an example, an LMF may manage the overall co-ordination andscheduling of resources required for the location of a UE that isregistered with or accessing 5GCN. It may calculate or verify a finallocation and any velocity estimate and may estimate the achievedaccuracy. The LMF may receive location requests for a target UE from theserving AMF using the Nlmf interface. The LMF may interact with the UEin order to exchange location information applicable to UE assisted andUE based position methods. The LMF may interact with the NG-RAN, N3IWFor TNAN in order to obtain location information. The LMF may determinethe result of the positioning in geographical co-ordinates. If requestedand if available, the positioning result may comprise the velocity ofthe UE. The LMF may perform additional functions to support locationservices. For example, the LMF may support a request for a singlelocation received from a serving AMF for a target UE. For example, theLMF may support a request for periodic or triggered location receivedfrom a serving AMF for a target UE. For example, the LMF may determineposition methods based on UE and PLMN capabilities, QoS and LCS Clienttype. For example, the LMF may report UE location estimates directly toa GMLC for periodic or triggered location of a target UE. For example,the LMF may support cancelation of periodic or triggered location for atarget UE. For example, the LMF may support the provision of broadcastassistance data to UEs via NG-RAN in ciphered or unciphered form andforward any ciphering keys to subscribed UEs via the AMF.

In an example, LMF selection functionality may be used by the AMF todetermine an LMF for location estimation of the target UE. If an LMF IDis available in the UE location context or provided by the UE, the AMFmay first evaluate if the LMF identified by the LMF ID can be used. TheLMF selection functionality may be supported by the LMF if it determinesthat it is unsuitable or unable to support location for the current UEaccess network or serving cell for the deferred 5GC-MT-LR procedure forperiodic, or triggered location events. LMF reselection may be afunctionality supported by AMF when necessary, e.g. due to UE mobility.The AMF may select a new LMF if the AMF determines that LMF identifiedby the LMF ID may not be used. The AMF may select a new LMF if the LMFID is not available in the UE location context. The AMF may select a newLMF if the LMF ID is not provided by the UE. The LMF selection may beperformed at the AMF or LMF based on the locally available informationi.e. LMF profiles are configured locally at AMF or LMF, or by queryingNRF. LMF selection may performed when a location request is received atthe AMF and the AMF determines to use the LMF for UE positionestimation. LMF selection may performed when the subscribed UE eventreporting is received. In an example, requested quality of serviceinformation may be considered for LMF selection, e.g. LCS accuracy,response time (e.g. latency), and/or Access Type (e.g. 3GPP/N3GPP). Forexample, location methods may differ depending on the Access Type, e.g.in case of WLAN Access Location determination may just correspond toretrieval of IP addressing information from the N3IWF/TNGF; as anotherexample, for Wireline access, Location determination may just correspondto retrieval of geo coordinates corresponding to a Line Id. In anexample, RAT type (i.e. 5G NR or eLTE) and/or the serving AN node (i.e.gNB or NG-eNB) of the target UE may be considered for LMF selection. Inan example, RAN configuration information may be considered for LMFselection. In an example, LMF capabilities may be considered for LMFselection. In an example, LMF load may be considered for LMF selection.In an example, LMF location may be considered for LMF selection. In anexample, indication of either a single event report or multiple eventreports may be considered for LMF selection. In an example, duration ofevent reporting may be considered for LMF selection. In an example,network slicing information, e.g. S-NSSAI and/or NSI ID may beconsidered for LMF selection.

In an example, LCS Quality of Service may be used to characterize thelocation request. It may either be determined by the operator ordetermined based on the negotiation with the LCS client or the AF. Itmay be optional for LCS client or the AF to provide the LCS Quality ofService in the location request. LCS Quality of Service information maybe characterized by 3 key attributes: LCS QoS class, accuracy, and/orresponse time. The LCS QoS class may define the degree of adherence bythe Location Service to another quality of service parameter (e.g.accuracy), if requested. The 5G system may attempt to satisfy the otherquality of service parameter regardless of the use of QoS class. Theremay be 2 LCS QoS classes, Best Effort class and/or Assured class. Forexample, a Best Effort class may define the least stringent requirementon the QoS achieved for a location request. If a location estimateobtained does not fulfil the other QoS requirements, it may still bereturned but with an appropriate indication that the requested QoS wasnot met. If no location estimate is obtained, an appropriate error causemay be sent. For example, Assured class may define the most stringentrequirement on the accuracy achieved for a location request. If alocation estimate obtained does not fulfil the other QoS requirements,then it may be discarded, and an appropriate error cause may be sent.

FIG. 21 is an example diagram depicting Performance requirements fordifferent positioning service levels as per an aspect of an embodimentof the present disclosure.

Adaptability and flexibility may be among the key features of the 5Gsystem to serve a wide diversity of verticals and services, in differentenvironments (e.g. rural, urban, indoor). This may apply to highaccuracy positioning and translates into the ability to satisfydifferent levels of services and requirements, for instance onperformance (e.g. accuracy, positioning service availability,positioning service latency) and on functionality (e.g. security). The5G System may provide different 5G positioning services withconfigurable performances working points (e.g. accuracy, positioningservice availability, positioning service latency, energy consumption,update rate, TTFF) according to the needs of users, operators and thirdparties. The 5G system may support the combination of 3GPP and non-3GPPpositioning technologies to achieve performances of the 5G positioningservices better than those achieved using only 3GPP positioningtechnologies. For instance, the combination of 3GPP positioningtechnologies with non-3GPP positioning technologies such as GNSS (e.g.Beidou, Galileo, GLONASS, and GPS), Terrestrial Beacon Systems (TBS),sensors (e.g. barometer, IMU), WLAN/Bluetooth-based positioning, maysupport the improvement of accuracy, positioning service availability,reliability and/or confidence level, the reduction of positioningservice latency, the increase of the update rate of the position-relateddata, increase the coverage (service area). The combination may varyover time to optimize the performances and may be the combination ofmultiple positioning technologies at the same epoch and/or thecombination of multiple positioning technologies at different epochs.The corresponding positioning information may be acquired in a timelyfashion, be reliable, and be available (e.g. it is possible to determinethe position). UEs may be able to share positioning information betweeneach other e.g. to a controller if the location information cannot beprocessed or used locally.

The 5G system may be able to provide positioning services with theperformances requirements in FIG. 21 . The requirements may not precludeany type of UE, including specific UE such as for example V2X, MTC. The5G system may be able to provide the 5G positioning services with a TimeTo First Fix (TTFF) less than 30 s (e.g. 30 seconds) and, for some 5Gpositioning services, may support mechanisms to provide a TTFF less than10 s. In some services, a TTFF of less than 10 s may only be achievableat the expense of a relaxation of some other performances (e.g.horizontal accuracy may be 1 m or 3 m after 10 s TTFF, and reach asteady state accuracy of 0.3 m after 30 s). The 5G system may support amechanism to determine the UE's velocity with a positioning serviceavailability of 99%, an accuracy better than 0.5 m/s for the speed andan accuracy better than 5 degree for the 3-Dimension direction oftravel. The 5G system may support a mechanism to determine the UE'sheading with an accuracy better than 30 degrees (0.54 rad) and apositioning service availability of 99.9% for static users and with anaccuracy better than 10 degrees (0.17 rad) and a positioning serviceavailability of 99% for users up to 10 km/h.

The 5G system may support positioning technologies that allow the UE tooperate at Service Level 1 for at least 12 years using less than 1800mWh of battery capacity, assuming multiple position updates per hour.This requirement aims energy-efficient positioning technologies draininga minimal energy on the UE battery. It derives from use cases, such asasset tracking, with a small form-factor battery representative of anIoT device. This requirement may translate into an energy consumptionfor the UE's positioning functions in the order of 20 mJ per fix. Thisrequirement may not preclude the use of higher energy consumption tofulfil higher position update rates than the one above, or other KPIsthan those of Service Level 1 (e.g. more accurate service levels).

In existing technologies, a communication system (e.g. 5G) may notexpose its positioning capability (e.g. capability of positioningservice level and/or capability of positioning service area) to anapplication (e.g. an LCS client, a third party application). Theapplication may not be able to request a positioning service leveland/or positioning service area based on the positioning capability ofthe communication system. Consequently, the application may not obtainthe desired positioning service level and/or positioning service area.This may prevent the application from obtaining the positioninginformation of the wireless device efficiently, and may degrade theperformance of time sensitive applications (e.g. V2X communication, UAVapplication).

In existing technologies, an LCS client may not be able to negotiatepositioning capability with a communication system. The communicationsystem may reject a positioning request from the LCS client withoutproviding an accepted positioning service level and/or positioningservice area. Consequently, the LCS client may request positioninginformation again and receive another reject from the communicationsystem.

The existing technologies may not enable a communication system todetermine at least one positioning method to support a positioningservice level and/or positioning service area requested by an LCSclient, consequently, the LCS client may not get the positioning servicefrom a communication system.

Example embodiments of the present disclosure may provide enhancedmechanisms to support positioning service level control and/orpositioning service area control. Example embodiments of the presentdisclosure may provide enhanced mechanisms to enable a communicationsystem to expose its positioning capability to an application, theapplication may be able to request a positioning service level and/orpositioning service area based on the positioning capability of thecommunication system. Example embodiments of the present disclosure mayprovide enhanced mechanisms to enable an LCS client to negotiatepositioning capability with a communication system, and thecommunication system may provide an accepted positioning service leveland/or positioning service area to the LCS client. Example embodimentsof the present disclosure may provide enhanced mechanisms to enable acommunication system to determine at least one positioning method tosupport a positioning service level and/or positioning service arearequested by an LCS client, and the LCS client may get the positioningservice from a communication system accordingly.

FIG. 22 shows an example call flow which may comprise one or moreactions. In an example, a UE may send a message (e.g. a LPP message, forexample, a ProvideCapabilities message)) to an LMC/LMF, theProvideCapabilities message may comprise at least one of: UE positioningcapability information, UE service area information, and/or UE velocityinformation. FIG. 23 is an example diagram depicting aProvideCapabilities message body. In an example, the UE positioningcapability information may indicate positioning capability supported bythe UE. In an example, the UE positioning capability information mayindicate one or more positioning methods supported by the UE. Forexample, the UE positioning capability information may comprise at leastone of the following positioning capabilities and/or positioning methodssupported by the UE: a parameter (e.g. ecid-ProvideCapabilities,nr-ECID-ProvideCapabilities-r16 in FIG. 23 ) indicating support ofEnhanced Cell Identity (ECID) capability; a parameter (e.g.otdoa-ProvideCapabilities, NR-DL-TDOA-ProvideCapabilities-r16,NR-DL-AoD-ProvideCapabilities-r16 in FIG. 23 ) indicating support ofObserved Time Difference of Arrival (OTDOA) capability; a parameter(e.g. a-gnss-ProvideCapabilities in FIG. 23 ) indicating support ofnetwork-assisted GNSS methods; a parameter (e.g.wlan-ProvideCapabilities-r13 in FIG. 23 ) indicating support of WLANpositioning; a parameter (e.g. bt-ProvideCapabilities-r13 in FIG. 23 )indicating support of Bluetooth positioning; a parameter (e.g.tbs-ProvideCapabilities-r13 in FIG. 23 ) indicating support ofTerrestrial Beacon System (TBS) positioning; a parameter (e.g.Sensor-ProvideCapabilities) indicating support of barometric pressuresensor (BPS) positioning; a parameter (e.g.nr-Multi-RTT-ProvideCapabilities-r16 in FIG. 23 ) indicating support ofmultiple RTT positioning (e.g. the multiple RTT positioning may compriseat least one of: NR multiple RTT measurement, NR uplink SRS measurement,and/or NR downlink PRS measurement); a parameter (e.g.no-Support-Capability in FIG. 23 ) indicating no support of apositioning capability. In an example, the ProvideCapabilities messagemay comprise a parameter (e.g. ue-ServiceArea in FIG. 23 ) indicating UEservice area information. The UE service area information may indicateUE service area, for example, indoor area and/or outdoor area. Theoutdoor area may comprise rural area, urban area, and/or dense urbanarea. In an example, the ProvideCapabilities message may comprise aparameter (e.g. ue-Velocity in FIG. 23 ) indicating UE velocityinformation. For example, the UE velocity information may indicate thevelocity of the UE. For example, the UE velocity information mayindicate horizontal velocity and/or the vertical velocity. For example,the UE velocity information may comprise the speed and/or the directionof the UE.

In response to the message received from the UE, the LMC/LMF may send amessage (e.g. UE capability notification) to a network function (e.g. aUDM, OAM), the UE capability notification message may comprise one ormore parameters of the ProvideCapabilities message (e.g. UE positioningcapability information, UE service area information, and/or UE velocityinformation).

In an example, the UE may send a message (e.g. a NAS message, forexample, a REGISTRATION REQUEST message)) to an AMF, the REGISTRATIONREQUEST message may comprise at least one of: UE positioning capabilityinformation, UE service area information, and/or UE velocityinformation. FIG. 24 is an example diagram depicting a REGISTRATIONREQUEST message body. In response to the message received from the UE,the AMF may send a message (e.g. UE capability notification) to anetwork function (e.g. a UDM, OAM), the UE capability notificationmessage may comprise one or more parameters of the REGISTRATION REQUESTmessage (e.g. UE positioning capability information, UE service areainformation, and/or UE velocity information).

In an example, a (R)AN may send to the LMC/LMF a message (e.g. a NRPPamessage, for example, a Positioning Capability Report message), thePositioning Capability Report message may comprise at least one of:(R)AN positioning capability information, UE positioning capabilityinformation, UE service area information, and/or UE velocityinformation. FIG. 25 is an example diagram depicting a PositioningCapability Report message body. In an example, the (R)AN positioningcapability information may indicate positioning capability supported bythe (R)AN. In an example, the (R)AN positioning capability informationmay indicate one or more positioning methods supported by the (R)AN. Forexample, the (R)AN positioning capability information may comprise atleast one of the following positioning capabilities and/or positioningmethods supported by the (R)AN: a parameter indicating support ofEnhanced Cell Identity (ECID) capability; a parameter indicating supportof Observed Time Difference of Arrival (OTDOA) capability; a parameterindicating support of UL RTOA (uplink relative time of arrival); aparameter indicating support of UL RSRP (uplink reference signalreceived power) measurements; a parameter indicating support of uplinkAngle of Arrival (UL AoA) measurements (e.g. Azimuth and/or ZenithAngles); a parameter indicating support of multiple RTT positioning(e.g. the multiple RTT positioning may comprise at least one of: NRmultiple RTT measurement, NR uplink SRS measurement); a parameterindicating support of gNB RX-TX time difference measurements; aparameter indicating no support of a positioning capability.

In response to the message received from the (R)AN, the LMC/LMF may senda message (e.g. (R)AN capability notification) to a network function(e.g. a UDM, OAM), the (R)AN capability notification message maycomprise one or more parameters of the Positioning Capability Reportmessage (e.g. (R)AN positioning capability information, UE positioningcapability information, UE service area information, and/or UE velocityinformation). In an example, the LMC/LMF may receive (R)AN positioningcapability information of one or more base stations from the one or morebase stations in a registration area of the wireless device. The LMC/LMFmay send the (R)AN positioning capability information of one or morebase stations to the network function.

In an example, a (R)AN may send to the AMF a message (e.g. an N2message), the N2 message may comprise at least one of: N2 parameters, aRegistration Request message, (R)AN positioning capability information,UE positioning capability information, UE service area information,and/or UE velocity information. For example, the N2 parameters maycomprise a selected PLMN ID (or PLMN ID and NID), Location Informationand Cell Identity related to the cell in which the UE is camping, UEContext Request which may indicate that a UE context including securityinformation needs to be setup at the NG-RAN. For example, the N2parameters may comprise an Establishment cause, a CAG Identifier if theUE is accessing the NG-RAN using a CAG cell and IAB-Indication if theindication is received in AN parameters from the UE. For example, theRegistration Request message may comprise at least one of: aRegistration type, a UE identity (e.g. SUCI, 5G-GUTI or PEI), lastvisited TAI (if available), Security parameters, Requested NSSAI,Mapping Of Requested NSSAI, Default Configured NSSAI Indication, UERadio Capability Update, UE MM Core Network Capability, PDU Sessionstatus, List Of PDU Sessions To Be Activated, Follow-on request, MICOmode preference, Requested Active Time, Requested DRX parameters,extended idle mode DRX parameters, LADN DNN(s) or Indicator OfRequesting LADN Information, NAS message container, Support forrestriction of use of Enhanced Coverage, Preferred Network Behaviour, UEPolicy Container (e.g. list of PSIs, indication of UE support for ANDSPand the operating system identifier) and/or UE Radio Capability ID.

In response to the message received from the (R)AN, the AMF may send amessage (e.g. (R)AN capability notification) to a network function (e.g.a UDM, OAM), the (R)AN capability notification message may comprise oneor more parameters of the N2 message (e.g. (R)AN positioning capabilityinformation, UE positioning capability information, UE service areainformation, and/or UE velocity information). In an example, the AMF mayreceive (R)AN positioning capability information of one or more basestations from the one or more base stations in a registration area ofthe wireless device. The AMF may send the (R)AN positioning capabilityinformation of the one or more base stations to the network function.

In an example, a gateway mobile location center (GMLC) may receive amessage (e.g. Positioning Capability Request) from a location services(LCS) client, the Positioning Capability Request message may indicatingrequesting/querying at least one of: capability of positioning servicelevel, supported positioning service area (e.g. supported 5G positioningservice area), and/or supported enhanced positioning service area (e.g.5G enhanced positioning service area). The capability of positioningservice level, the supported positioning service area, and/or thesupported enhanced positioning service area may be applied for the UEand/or for a PLMN, wherein the UE registers to the PLMN. In an example,the Positioning Capability Request message may comprise one or moreinformation elements/parameters. For example, the Positioning CapabilityRequest message may comprise at least one of: the UE identity (e.g.SUCI, SUPI, 5G-GUTI or PEI), a PLMN identifier, an LCS client type, aparameter indicating requesting/querying the capability of positioningservice level, a parameter indicating requesting/querying the supportedpositioning service area, and/or a parameter indicatingrequesting/querying the supported enhanced positioning service area.

In response to the message received from the LCS client, the GMLC maysend a message (e.g. Nudm_UECM_Get Request, Positioning CapabilityQuery) to a network function. The network function may be an AMF, a UDM,and/or an OAM. For example, the GMLC may send a Nudm_UECM_Get Requestmessage to a (home) UDM of the UE. The Nudm_UECM_Get Request message maycomprise the one or more information elements/parameters of thePositioning Capability Request message described above, for example, theUE identity, the PLMN identifier, and/or a parameter indicatingrequesting/querying the capability of positioning service level. In anexample, the Nudm_UECM_Get Request message may comprise a parameterindicating requesting/querying (R)AN positioning capability. In anexample, the Nudm_UECM_Get Request message may comprise a parameterindicating requesting/querying UE positioning capability.

In response to the message received from the GMLC, the UDM may take oneor more actions. In an example action, the UDM may have already receivedfrom the LMC/LMF and/or AMF at least one of the following information:(R)AN positioning capability information of at least one base station ina registration area of the wireless device, UE positioning capabilityinformation, UE service area information, and/or UE velocityinformation, the UDM may send a response message (e.g. Nudm_UECM_GetResponse) to the GMLC, the Nudm_UECM_Get Response message may compriseat least one of: (R)AN positioning capability information of the atleast one base station, UE positioning capability information, UEservice area information, and/or UE velocity information. In an example,based on local configuration, the Nudm_UECM_Get Response message maycomprise at least one of: a parameter indicating supported positioningservice level for the UE and/or the PLMN; a parameter indicatingsupported positioning service area, and/or a parameter indicating thesupported enhanced positioning service area.

In an example action, the UDM may send a message (e.g. PositioningCapability Query) to the LMC/LMF. For example, the PositioningCapability Query message may indicate requesting/querying UE positioningcapability and/or (R)AN positioning capability. For example, thePositioning Capability Query message may comprise one or moreinformation elements/parameters of the Nudm_UECM_Get Request messagedescribed above, for example, the UE identity, the PLMN identifier,and/or a parameter indicating requesting/querying the capability ofpositioning service level. In response to the message received from theUDM, the LMC/LMF may send a response message (e.g. PositioningCapability Query Response) to the UDM, the Positioning Capability QueryResponse message may comprise at least one of: (R)AN positioningcapability information of the at least one base station, UE positioningcapability information, UE service area information, and/or UE velocityinformation.

In an example action, the UDM may send a message (e.g. PositioningCapability Request) to the AMF. For example, the Positioning CapabilityRequest message may indicate requesting/querying UE positioningcapability and/or (R)AN positioning capability. For example, thePositioning Capability Request message may comprise one or moreinformation elements/parameters of the Nudm_UECM_Get message describedabove, for example, the UE identity, the PLMN identifier, and/or aparameter indicating requesting/querying the capability of positioningservice level. In response to the message received from the UDM, the AMFmay send a response message (e.g. Positioning Capability Response) tothe UDM, the Positioning Capability Response message may comprise atleast one of: (R)AN positioning capability information of the at leastone base station, UE positioning capability information, UE service areainformation, and/or UE velocity information.

In response to the message received from the LMC/LMF and/or AMF, and/orin response to the message received from the GMLC, the UDM may send aresponse message (e.g. Nudm_UECM_Get Response) to the GMLC. TheNudm_UECM_Get Response message may comprise at least one of: (R)ANpositioning capability information of the at least one base station, UEpositioning capability information, UE service area information, and/orUE velocity information. In an example, based on local configuration,the Nudm_UECM_Get Response message may comprise at least one of: aparameter indicating supported positioning service level for the UEand/or the PLMN; a parameter indicating supported positioning servicearea (e.g. indoor, outdoor), and/or a parameter indicating the supportedenhanced positioning service area.

In response to the message received from the network function (e.g. theUDM), the GMLC may take one or more actions. In an example action, basedon the message received from the network function and/or based on localconfiguration, the GMLC may determine at least one of: supportedcapability of positioning service level for the UE and/or the PLMN,supported positioning service area for the UE and/or the PLMN, and/orsupported enhanced positioning service area for the UE and/or the PLMN.For example, based on the (R)AN positioning capability information ofthe at least one base station, the UE positioning capabilityinformation, the UE service area information, and/or the UE velocityinformation, the GMLC may determine at least one of: supportedcapability of positioning service level, supported positioning servicearea, and/or supported enhanced positioning service area.

In an example, the supported capability of positioning service level mayindicate a supported positioning service level. In an example, thesupported capability of positioning service level may comprise at leastone of: a parameter indicating positioning service level number (e.g. 1,2, . . . 7); a parameter indicating an absolute or a relativepositioning; a parameter indicating a horizontal accuracy; a parameterindicating a vertical accuracy; a parameter indicating a positioningservice availability; a parameter indicating a positioning servicelatency; a parameter indicating a 5G positioning service area; and/or aparameter indicating a 5G enhanced positioning service area. In anexample, the supported positioning service area may indicate coverage,environment of use and/or UE velocity. For example, the supportedpositioning service area may indicate supported indoor and/or outdoorcoverage. For example, the supported positioning service area mayindicate supported UE speed in the indoor and/or outdoor coverage. Forexample, the supported enhanced positioning service area may indicatesupported indoor and/or outdoor coverage. For example, the supportedenhanced positioning service area may indicate supported UE speed in theindoor and/or outdoor coverage. In an example, the supported capabilityof positioning service level may be used independently. In an example,the supported capability of positioning service level may be used withthe supported positioning service area and/or the supported enhancedpositioning service area together. FIG. 21 shows example definition ofsupported capability of positioning service level, supported positioningservice area, and/or supported enhanced positioning service area. InFIG. 21 , Positioning service level is an example of supportedcapability of positioning service level, 5G positioning service area isan example of supported positioning service area, 5G enhancedpositioning service area is an example of supported enhanced positioningservice area.

In an example, the (R)AN positioning capability information of the atleast one base station may indicate that the (R)AN supports ECID(capability and/or positioning method), the UE positioning capabilityinformation may indicate that the UE supports ECID (capability and/orpositioning method) and/or OTDOA (capability and/or positioning method),the UE service area information may indicate UE is in an indoor area,the UE velocity information may indicate the speed of UE is 30 km/h,based on above information, the GMLC may determine at least one of: asupported capability of positioning service level 1 for the UE and/orthe PLMN; a supported positioning service area where UE may have a speedup to 30 km/h for indoor environment, and up to 250 km/h for outdoor(rural and urban) environment; and/or a supported enhanced positioningservice area where UE may have a speed up to 30 km/h for indoorenvironment. As shown in FIG. 21 , the supported capability ofpositioning service level 1 may have a horizontal accuracy of 10 metersand a vertical accuracy of 3 meters.

In an example, the (R)AN positioning capability information of the atleast one base station may indicate that the (R)AN supports ECID and/orOTDOA, the UE positioning capability information may indicate that theUE supports ECID, OTDOA, WLAN positioning, and/or Bluetooth positioning,the UE service area information may indicate UE is in an outdoor area,the UE velocity information may indicate the speed of UE is 300 km/h,based on above information, the GMLC may determine at least one of: asupported capability of positioning service level 2 for the UE and/orthe PLMN; a supported positioning service area where UE may have a speedup to 500 km/h for outdoor environment. As shown in FIG. 21 , thesupported capability of positioning service level 2 may have ahorizontal accuracy of 3 meters and a vertical accuracy of 3 meters.

In an example, the (R)AN positioning capability information of the atleast one base station may indicate that the (R)AN supports ECID and/orOTDOA, the UE positioning capability information may indicate that theUE supports ECID, OTDOA, WLAN positioning, and/or high accuracy (HA)GNSS (e.g. Real-time kinematic (RTK) positioning), the UE service areainformation may indicate UE is in an indoor area, the UE velocityinformation may indicate the speed of UE is 30 km/h, based on aboveinformation, the GMLC may determine at least one of: a supportedcapability of positioning service level 7 for the UE and/or the PLMN; asupported positioning service area where UE may have a speed up to 30km/h for indoor and outdoor environment; and/or a supported enhancedpositioning service area where UE may have a speed up to 30 km/h forindoor and outdoor environment. As shown in FIG. 21 , the supportedcapability of positioning service level 7 may have a horizontal accuracyof 0.2 meters and a vertical accuracy of 0.2 meters.

In an example action, in response to the message received from the LCSclient, the GMLC may send to the LCS client a response message (e.g.Positioning Capability Response). The Positioning Capability Responsemessage may comprise the supported capability of positioning servicelevel, supported positioning service area, and/or supported enhancedpositioning service area.

In response to the message received from the GMLC, the LCS client maytake one or more actions. In an example action, based on the supportedcapability of positioning service level, supported positioning servicearea, and/or supported enhanced positioning service area, the LCS clientmay determine one or more requested parameters for a positioning requestmessage. For example, the determined one or more requested parametersmay equal to the supported capability of positioning service level, thesupported positioning service area, and/or the supported enhancedpositioning service area. For example, the determined one or morerequested parameters may different from (e.g. less than) the supportedcapability of positioning service level, the supported positioningservice area, and/or the supported enhanced positioning service area.For example, the determined one or more requested parameters maycomprise at least one of: a requested positioning service level, arequested positioning service area, a requested enhanced positioningservice area, a requested horizontal positioning accuracy, a requestedvertical positioning accuracy, and/or a requested QoS. In an exampleaction, the LCS client may send to the GMLC a message (e.g. positioningrequest message). The positioning request message may indicaterequesting positioning information of the UE. The positioning requestmessage may comprise the determined one or more requested parameters.FIG. 26 is an example diagram depicting the procedures of a GMLC as peran aspect of an embodiment of the present disclosure.

FIG. 27 shows an example call flow which may comprise one or moreactions. In an example, a UE may send a message (e.g. a LPP message, forexample, a ProvideCapabilities message)) to an LMC/LMF, theProvideCapabilities message may comprise at least one of: UE positioningcapability information, UE service area information, and/or UE velocityinformation. These processes may be similar to the processes describedabove with respect to FIG. 22 . For brevity, further description willnot be repeated here.

In response to the message received from the UE, the LMC/LMF may send amessage (e.g. UE capability notification) to a network function (e.g.,an AMF, a UDM, OAM), the UE capability notification message may compriseone or more parameters of the ProvideCapabilities message (e.g. UEpositioning capability information, UE service area information, and/orUE velocity information).

In an example, the UE may send a message (e.g. a NAS message, forexample, a REGISTRATION REQUEST message)) to an AMF, the REGISTRATIONREQUEST message may comprise at least one of: UE positioning capabilityinformation, UE service area information, and/or UE velocityinformation.

In an example, a (R)AN may send to the LMC/LMF a message (e.g. a NRPPamessage, for example, a Positioning Capability Report message), thePositioning Capability Report message may comprise at least one of:(R)AN positioning capability information, UE positioning capabilityinformation, UE service area information, and/or UE velocityinformation. These processes may be similar to the processes describedabove with respect to FIG. 22 . For brevity, further description willnot be repeated here.

In response to the message received from the (R)AN, the LMC/LMF may senda message (e.g. (R)AN capability notification) to a network function(e.g. the AMF, UDM, OAM), the (R)AN capability notification message maycomprise one or more parameters of the Positioning Capability Reportmessage (e.g. (R)AN positioning capability information, UE positioningcapability information, UE service area information, and/or UE velocityinformation). In an example, the LMC/LMF may receive (R)AN positioningcapability information of one or more base stations from the one or morebase stations in a registration area of the wireless device. The LMC/LMFmay send the (R)AN positioning capability information of one or morebase stations to the network function.

In an example, a (R)AN may send to the AMF a message (e.g. an N2message), the N2 message may comprise at least one of: N2 parameters, aRegistration Request message, (R)AN positioning capability information,UE positioning capability information, UE service area information,and/or UE velocity information. For example, the N2 parameters maycomprise a selected PLMN ID (or PLMN ID and NID), Location Informationand Cell Identity related to the cell in which the UE is camping, UEContext Request which may indicate that a UE context including securityinformation needs to be setup at the NG-RAN. For example, the N2parameters may comprise an Establishment cause, a CAG Identifier if theUE is accessing the NG-RAN using a CAG cell and IAB-Indication if theindication is received in AN parameters from the UE. For example, theRegistration Request message may comprise at least one of: aRegistration type, a UE identity (e.g. SUCI, 5G-GUTI or PEI), lastvisited TAI (if available), Security parameters, Requested NSSAI,Mapping Of Requested NSSAI, Default Configured NSSAI Indication, UERadio Capability Update, UE MM Core Network Capability, PDU Sessionstatus, List Of PDU Sessions To Be Activated, Follow-on request, MICOmode preference, Requested Active Time, Requested DRX parameters,extended idle mode DRX parameters, LADN DNN(s) or Indicator OfRequesting LADN Information, NAS message container, Support forrestriction of use of Enhanced Coverage, Preferred Network Behaviour, UEPolicy Container (e.g. list of PSIs, indication of UE support for ANDSPand the operating system identifier) and/or UE Radio Capability ID.

In an example, a gateway mobile location center (GMLC) may receive amessage (e.g. Positioning Capability Request) from a location services(LCS) client, the Positioning Capability Request message may indicatingrequesting/querying at least one of: capability of positioning servicelevel, supported positioning service area (e.g. supported 5G positioningservice area), and/or supported enhanced positioning service area (e.g.5G enhanced positioning service area). The capability of positioningservice level, the supported positioning service area, and/or thesupported enhanced positioning service area may be applied for the UEand/or for a PLMN, wherein the UE registers to the PLMN. In an example,the Positioning Capability Request message may comprise one or moreinformation elements/parameters. For example, the Positioning CapabilityRequest message may comprise at least one of: the UE identity (e.g.SUCI, SUPI, 5G-GUTI or PEI), a PLMN identifier, an LCS client type, aparameter indicating requesting/querying the capability of positioningservice level, a parameter indicating requesting/querying the supportedpositioning service area, and/or a parameter indicatingrequesting/querying the supported enhanced positioning service area.

In response to the message received from the LCS client, the GMLC maysend a message (e.g. Positioning Capability Query) to a networkfunction. The network function may be an AMF, a UDM, and/or an OAM. Forexample, the GMLC may send a Positioning Capability Query message to theAMF, where the AMF is serving for the UE. The Positioning CapabilityQuery message may comprise the one or more informationelements/parameters of the Positioning Capability Request messagedescribed above, for example, the UE identity, the PLMN identifier, theparameter indicating requesting/querying the capability of positioningservice level, the parameter indicating requesting/querying thesupported positioning service area, and/or the parameter indicatingrequesting/querying the supported enhanced positioning service area.

In response to the message received from the GMLC, the AMF may take oneor more actions. In an example action, the AMF may have already receivedfrom the UE, the at least one base station and/or the LMC/LMF, at leastone of the following information: (R)AN positioning capabilityinformation of the at least one base station, UE positioning capabilityinformation, UE service area information, and/or UE velocityinformation.

In an example action, the AMF may send a message (e.g. PositioningCapability Query) to the UDM/OAM. For example, the PositioningCapability Query message may indicate requesting/querying UE positioningcapability and/or (R)AN positioning capability. For example, thePositioning Capability Query message may comprise at least one of: theUE identity, the PLMN identifier, a parameter indicatingrequesting/querying UE positioning capability, a parameter indicatingrequesting/querying (R)AN positioning capability, a parameter indicatingrequesting/querying the capability of positioning service level, aparameter indicating requesting/querying UE service area information, aparameter indicating requesting/querying UE velocity information.

In response to the message received from the AMF, the UDM/OAM may send aresponse message (e.g. Positioning Capability Query Response) to theAMF. For example, the Positioning Capability Query Response message maycomprise at least one of: the UE identity, the PLMN identifier, (R)ANpositioning capability information of the at least one base station, UEpositioning capability information, UE service area information, UEvelocity information, a parameter indicating supported positioningservice level for the UE and/or the PLMN; a parameter indicatingsupported positioning service area (e.g. indoor, outdoor), and/or aparameter indicating the supported enhanced positioning service area.

In response to the message received from the UDM/OAM, the AMF may takeone or more actions. In an example action, based on the message receivedfrom the UDM/OAM, UE, (R)AN, LMC/LMF and/or based on localconfiguration, the AMF may determine at least one of: supportedcapability of positioning service level for the UE and/or the PLMN,supported positioning service area for the UE and/or the PLMN, and/orsupported enhanced positioning service area for the UE and/or the PLMN.For example, based on the (R)AN positioning capability information ofthe at least one base station, the UE positioning capabilityinformation, the UE service area information, and/or the UE velocityinformation, the AMF may determine at least one of: supported capabilityof positioning service level, supported positioning service area, and/orsupported enhanced positioning service area. The definition(s) and/orthe content(s) of the supported capability of positioning service level,supported positioning service area, and/or supported enhancedpositioning service area may be similar to the definition(s) and/or thecontent(s) described above with respect to FIG. 22 . For brevity,further description will not be repeated here.

In an example, the supported capability of positioning service level mayindicate a supported positioning service level. In an example, thesupported capability of positioning service level may comprise at leastone of: a parameter indicating an absolute or a relative positioning; aparameter indicating a horizontal accuracy; a parameter indicating avertical accuracy; a parameter indicating a positioning serviceavailability; a parameter indicating a positioning service latency; aparameter indicating a 5G positioning service area; and/or a parameterindicating a 5G enhanced positioning service area. In an example, thesupported positioning service area may indicate coverage, environment ofuse and/or UE velocity. For example, the supported positioning servicearea may indicate supported indoor and/or outdoor coverage. For example,the supported positioning service area may indicate supported UE speedin the indoor and/or outdoor coverage. For example, the supportedenhanced positioning service area may indicate supported indoor and/oroutdoor coverage. For example, the supported enhanced positioningservice area may indicate supported UE speed in the indoor and/oroutdoor coverage. In an example, the supported capability of positioningservice level may be used independently. In an example, the supportedcapability of positioning service level may be used with the supportedpositioning service area and/or the supported enhanced positioningservice area together. FIG. 21 shows example definition of supportedcapability of positioning service level, supported positioning servicearea, and/or supported enhanced positioning service area.

In an example, the (R)AN positioning capability information of the atleast one base station may indicate that the (R)AN supports OTDOA(capability and/or positioning method), the UE positioning capabilityinformation may indicate that the UE supports ECID (capability and/orpositioning method) and/or OTDOA (capability and/or positioning method),the UE service area information may indicate UE is in an indoor area,the UE velocity information may indicate the speed of UE is 30 km/h,based on above information, the AMF may determine at least one of: asupported capability of positioning service level 1 for the UE and/orthe PLMN; a supported positioning service area where UE may have a speedup to 30 km/h for indoor environment, and up to 250 km/h for outdoor(rural and urban) environment; and/or a supported enhanced positioningservice area where UE may have a speed up to 30 km/h for indoorenvironment.

In an example, the (R)AN positioning capability information of the atleast one base station may indicate that the (R)AN supports ECID and/orOTDOA, the UE positioning capability information may indicate that theUE supports ECID, WLAN positioning, and/or TBS positioning, the UEservice area information may indicate UE is in an outdoor area, the UEvelocity information may indicate the speed of UE is 300 km/h, based onabove information, the GMLC may determine at least one of: a supportedcapability of positioning service level 2 for the UE and/or the PLMN; asupported positioning service area where UE may have a speed up to 500km/h for outdoor environment.

In an example, the (R)AN positioning capability information of the atleast one base station may indicate that the (R)AN supports ECID and/orOTDOA, the UE positioning capability information may indicate that theUE supports ECID, OTDOA, WLAN positioning, and/or high accuracy (HA)GNSS (e.g. Real-time kinematic (RTK) positioning), the UE service areainformation may indicate UE is in an indoor area, the UE velocityinformation may indicate the speed of UE is 30 km/h, based on aboveinformation, the AMF may determine at least one of: a supportedcapability of positioning service level 7 for the UE and/or the PLMN; asupported positioning service area where UE may have a speed up to 30km/h for indoor and outdoor environment; and/or a supported enhancedpositioning service area where UE may have a speed up to 30 km/h forindoor and outdoor environment.

In an example action, in response to the message received from the GMLC,the AMF may send to the GMLC a response message (e.g. PositioningCapability Response). The Positioning Capability Response message maycomprise the supported capability of positioning service level,supported positioning service area, and/or supported enhancedpositioning service area. In response to the message received from theAMF, and/or in response to the message received from the LCS client, theGMLC may send to the LCS client a response message (e.g. PositioningCapability Response). The Positioning Capability Response message maycomprise the supported capability of positioning service level,supported positioning service area, and/or supported enhancedpositioning service area.

In response to the message received from the GMLC, the LCS client maytake one or more actions. In an example action, based on the supportedcapability of positioning service level, supported positioning servicearea, and/or supported enhanced positioning service area, the LCS clientmay determine one or more requested parameters for a positioning requestmessage. For example, the determined one or more requested parametersmay equal to the supported capability of positioning service level, thesupported positioning service area, and/or the supported enhancedpositioning service area. For example, the determined one or morerequested parameters may different from (e.g. less than) the supportedcapability of positioning service level, the supported positioningservice area, and/or the supported enhanced positioning service area.For example, the determined one or more requested parameters maycomprise at least one of: a requested positioning service level, arequested positioning service area, a requested enhanced positioningservice area, a requested horizontal positioning accuracy, a requestedvertical positioning accuracy, and/or a requested QoS. In an exampleaction, the LCS client may send to the GMLC a message (e.g. positioningrequest message). The positioning request message may indicaterequesting positioning information of the UE. The positioning requestmessage may comprise the determined one or more requested parameters.FIG. 28 is an example diagram depicting the procedures of an AMF as peran aspect of an embodiment of the present disclosure.

FIG. 29 shows an example call flow which may comprise one or moreactions. In an example, a UE may send a message (e.g. a LPP message, forexample, a ProvideCapabilities message)) to an LMC/LMF, theProvideCapabilities message may comprise at least one of: UE positioningcapability information, UE service area information, and/or UE velocityinformation. These processes may be similar to the processes describedabove with respect to FIG. 22 . For brevity, further description willnot be repeated here.

In an example, the UE may send a message (e.g. a NAS message, forexample, a REGISTRATION REQUEST message)) to an AMF, the REGISTRATIONREQUEST message may comprise at least one of: UE positioning capabilityinformation, UE service area information, and/or UE velocityinformation.

In an example, a (R)AN may send to the LMC/LMF a message (e.g. a NRPPamessage, for example, a Positioning Capability Report message), thePositioning Capability Report message may comprise at least one of:(R)AN positioning capability information, UE positioning capabilityinformation, UE service area information, and/or UE velocityinformation. These processes may be similar to the processes describedabove with respect to FIG. 22 . For brevity, further description willnot be repeated here.

In an example, a (R)AN may send to the AMF a message (e.g. an N2message), the N2 message may comprise at least one of: N2 parameters, aRegistration Request message, (R)AN positioning capability information,UE positioning capability information, UE service area information,and/or UE velocity information. For example, the N2 parameters maycomprise a selected PLMN ID (or PLMN ID and NID), Location Informationand Cell Identity related to the cell in which the UE is camping, UEContext Request which may indicate that a UE context including securityinformation needs to be setup at the NG-RAN. For example, the N2parameters may comprise an Establishment cause, a CAG Identifier if theUE is accessing the NG-RAN using a CAG cell and IAB-Indication if theindication is received in AN parameters from the UE. For example, theRegistration Request message may comprise at least one of: aRegistration type, a UE identity (e.g. SUCI, 5G-GUTI or PEI), lastvisited TAI (if available), Security parameters, Requested NSSAI,Mapping Of Requested NSSAI, Default Configured NSSAI Indication, UERadio Capability Update, UE MM Core Network Capability, PDU Sessionstatus, List Of PDU Sessions To Be Activated, Follow-on request, MICOmode preference, Requested Active Time, Requested DRX parameters,extended idle mode DRX parameters, LADN DNN(s) or Indicator OfRequesting LADN Information, NAS message container, Support forrestriction of use of Enhanced Coverage, Preferred Network Behaviour, UEPolicy Container (e.g. list of PSIs, indication of UE support for ANDSPand the operating system identifier) and/or UE Radio Capability ID.

In response to the message received from the (R)AN, the AMF may send amessage (e.g. (R)AN capability notification) to a network function (e.g.a UDM, OAM), the (R)AN capability notification message may comprise oneor more parameters of the N2 message (e.g. (R)AN positioning capabilityinformation, UE positioning capability information, UE service areainformation, and/or UE velocity information). In an example, the AMF mayreceive (R)AN positioning capability information of one or more basestations from the one or more base stations in a registration area ofthe wireless device. The AMF may send the (R)AN positioning capabilityinformation of the one or more base stations to the network function.

In an example, a gateway mobile location center (GMLC) may receive amessage (e.g. Positioning Capability Request) from a location services(LCS) client, the Positioning Capability Request message may indicatingrequesting/querying at least one of: capability of positioning servicelevel, supported positioning service area (e.g. supported 5G positioningservice area), and/or supported enhanced positioning service area (e.g.5G enhanced positioning service area). The capability of positioningservice level, the supported positioning service area, and/or thesupported enhanced positioning service area may be applied for the UEand/or for a PLMN, wherein the UE registers to the PLMN. In an example,the Positioning Capability Request message may comprise one or moreinformation elements/parameters. For example, the Positioning CapabilityRequest message may comprise at least one of: the UE identity (e.g.SUCI, SUPI, 5G-GUTI or PEI), a PLMN identifier, an LCS client type, aparameter indicating requesting/querying the capability of positioningservice level, a parameter indicating requesting/querying the supportedpositioning service area, and/or a parameter indicatingrequesting/querying the supported enhanced positioning service area.

In response to the message received from the LCS client, the GMLC maysend a message (e.g. Positioning Capability Query) to a networkfunction. The network function may be an AMF, a UDM, and/or an OAM. Forexample, the GMLC may send a Positioning Capability Query message to theAMF, where the AMF is serving for the UE. The Positioning CapabilityQuery message may comprise the one or more informationelements/parameters of the Positioning Capability Request messagedescribed above, for example, the UE identity, the PLMN identifier, theparameter indicating requesting/querying the capability of positioningservice level, the parameter indicating requesting/querying thesupported positioning service area, and/or the parameter indicatingrequesting/querying the supported enhanced positioning service area.

In response to the message received from the GMLC, the AMF may send amessage (e.g. Positioning Capability Request) to the LMC/LMF, where theLMC/LMF is serving for the UE. The Positioning Capability Requestmessage may comprise one or more information elements/parameters of thePositioning Capability Query message described above, for example, theUE identity, the PLMN identifier, the parameter indicatingrequesting/querying the capability of positioning service level, theparameter indicating requesting/querying the supported positioningservice area, and/or the parameter indicating requesting/querying thesupported enhanced positioning service area.

In response to the message received from the AMF, the LMC/LMF may takeone or more actions. In an example action, the LMC/LMF may have alreadyreceived from the UE, and/or the at least one base station, at least oneof the following information: (R)AN positioning capability informationof the at least one base station, UE positioning capability information,UE service area information, and/or UE velocity information.

In an example action, the LMC/LMF may send a message (e.g. PositioningCapability Query) to a network function (e.g. AMF, UDM/OAM). Forexample, the LMC/LMF may send a Positioning Capability Query message toa UDM/OAM, the Positioning Capability Query message may indicaterequesting/querying UE positioning capability and/or (R)AN positioningcapability. For example, the Positioning Capability Query message maycomprise at least one of: the UE identity, the PLMN identifier, aparameter indicating requesting/querying UE positioning capability, aparameter indicating requesting/querying (R)AN positioning capability, aparameter indicating requesting/querying the capability of positioningservice level, a parameter indicating requesting/querying UE servicearea information, a parameter indicating requesting/querying UE velocityinformation.

In response to the message received from the LMC/LMF, the UDM/OAM maysend a response message (e.g. Positioning Capability Query Response) tothe LMC/LMF. For example, the Positioning Capability Query Responsemessage may comprise at least one of: the UE identity, the PLMNidentifier, (R)AN positioning capability information of the at least onebase station, UE positioning capability information, UE service areainformation, UE velocity information, a parameter indicating supportedpositioning service level for the UE and/or the PLMN; a parameterindicating supported positioning service area (e.g. indoor, outdoor),and/or a parameter indicating the supported enhanced positioning servicearea.

In response to the message received from the network function (e.g. theUDM/OAM), the LMC/LMF may take one or more actions. In an exampleaction, based on the message received from the network function and/orbased on local configuration, the LMC/LMF may determine at least one of:supported capability of positioning service level for the UE and/or thePLMN, supported positioning service area for the UE and/or the PLMN,and/or supported enhanced positioning service area for the UE and/or thePLMN. For example, based on the (R)AN positioning capability informationof the at least one base station, the UE positioning capabilityinformation, the UE service area information, and/or the UE velocityinformation, the LMC/LMF may determine at least one of: supportedcapability of positioning service level, supported positioning servicearea, and/or supported enhanced positioning service area.

The definition(s) and/or the content(s) of the supported capability ofpositioning service level, supported positioning service area, and/orsupported enhanced positioning service area may be similar to thedefinition(s) and/or the content(s) described above with respect to FIG.22 . For brevity, further description will not be repeated here.

In an example, the (R)AN positioning capability information of the atleast one base station may indicate that the (R)AN supports ECID(capability and/or positioning method), the UE positioning capabilityinformation may indicate that the UE supports ECID (capability and/orpositioning method) and/or OTDOA (capability and/or positioning method),the UE service area information may indicate UE is in an indoor area,the UE velocity information may indicate the speed of UE is 30 km/h,based on above information, the GMLC may determine at least one of: asupported capability of positioning service level 1 for the UE and/orthe PLMN; a supported positioning service area where UE may have a speedup to 30 km/h for indoor environment, and up to 250 km/h for outdoor(rural and urban) environment; and/or a supported enhanced positioningservice area where UE may have a speed up to 30 km/h for indoorenvironment.

In an example, the (R)AN positioning capability information of the atleast one base station may indicate that the (R)AN supports ECID and/orOTDOA, the UE positioning capability information may indicate that theUE supports ECID, OTDOA, WLAN positioning, and/or Bluetooth positioning,the UE service area information may indicate UE is in an outdoor area,the UE velocity information may indicate the speed of UE is 300 km/h,based on above information, the GMLC may determine at least one of: asupported capability of positioning service level 2 for the UE and/orthe PLMN; a supported positioning service area where UE may have a speedup to 500 km/h for outdoor environment.

In an example, the (R)AN positioning capability information of the atleast one base station may indicate that the (R)AN supports ECID and/orOTDOA, the UE positioning capability information may indicate that theUE supports ECID, OTDOA, WLAN positioning, and/or high accuracy (HA)GNSS (e.g. Real-time kinematic (RTK) positioning), the UE service areainformation may indicate UE is in an indoor area, the UE velocityinformation may indicate the speed of UE is 30 km/h, based on aboveinformation, the GMLC may determine at least one of: a supportedcapability of positioning service level 7 for the UE and/or the PLMN; asupported positioning service area where UE may have a speed up to 30km/h for indoor and outdoor environment; and/or a supported enhancedpositioning service area where UE may have a speed up to 30 km/h forindoor and outdoor environment.

In an example action, in response to the message received from the AMF,the LMC/LMF may send to the AMF a response message (e.g. PositioningCapability Response). The Positioning Capability Response message maycomprise the supported capability of positioning service level,supported positioning service area, and/or supported enhancedpositioning service area.

In response to the message received from the AMF, and/or in response tothe message received from the GMLC, the AMF may send to the GMLC aresponse message (e.g. Positioning Capability Response). The PositioningCapability Response message may comprise the supported capability ofpositioning service level, supported positioning service area, and/orsupported enhanced positioning service area. In response to the messagereceived from the AMF, and/or in response to the message received fromthe LCS client, the GMLC may send to the LCS client a response message(e.g. Positioning Capability Response). The Positioning CapabilityResponse message may comprise the supported capability of positioningservice level, supported positioning service area, and/or supportedenhanced positioning service area.

In response to the message received from the GMLC, the LCS client maytake one or more actions. In an example action, based on the supportedcapability of positioning service level, supported positioning servicearea, and/or supported enhanced positioning service area, the LCS clientmay determine one or more requested parameters for a positioning requestmessage. For example, the determined one or more requested parametersmay equal to the supported capability of positioning service level, thesupported positioning service area, and/or the supported enhancedpositioning service area. For example, the determined one or morerequested parameters may different from (e.g. less than) the supportedcapability of positioning service level, the supported positioningservice area, and/or the supported enhanced positioning service area.For example, the determined one or more requested parameters maycomprise at least one of: a requested positioning service level, arequested positioning service area, a requested enhanced positioningservice area, a requested horizontal positioning accuracy, a requestedvertical positioning accuracy, and/or a requested QoS. In an exampleaction, the LCS client may send to the GMLC a message (e.g. positioningrequest message). The positioning request message may indicaterequesting positioning information of the UE. The positioning requestmessage may comprise the determined one or more requested parameters.

FIG. 30 shows an example call flow which may comprise one or moreactions. In an example, a UE may send a message (e.g. a LPP message, forexample, a ProvideCapabilities message)) to an LMC/LMF, theProvideCapabilities message may comprise at least one of: UE positioningcapability information, UE service area information, and/or UE velocityinformation. These processes may be similar to the processes describedabove with respect to FIG. 22 . For brevity, further description willnot be repeated here. As shown in FIG. 30 , a dot line box may comprisethe LMC/LMF and a (R)AN, where the (R)AN is serving for the UE. The dotline box may indicate that the LMC/LMF may be co-located with the (R)AN.The dot line box may indicate that the LMC/LMF may not be co-locatedwith the (R)AN (e.g. the LMC/LMF may be deployed separately from the(R)AN).

In response to the message received from the UE, the LMC/LMF may send amessage (e.g. UE capability notification) to a network function (e.g. aUDM, OAM), the UE capability notification message may comprise one ormore parameters of the ProvideCapabilities message (e.g. UE positioningcapability information, UE service area information, and/or UE velocityinformation).

In an example, the UE may send a message (e.g. a NAS message, forexample, a REGISTRATION REQUEST message)) to an AMF, the REGISTRATIONREQUEST message may comprise at least one of: UE positioning capabilityinformation, UE service area information, and/or UE velocityinformation. In response to the message received from the UE, the AMFmay send a message (e.g. UE capability notification) to a networkfunction (e.g. a UDM, OAM), the UE capability notification message maycomprise one or more parameters of the REGISTRATION REQUEST message(e.g. UE positioning capability information, UE service areainformation, and/or UE velocity information).

In an example, a (R)AN may send to the LMC/LMF a message (e.g. a NRPPamessage, for example, a Positioning Capability Report message), thePositioning Capability Report message may comprise at least one of:(R)AN positioning capability information, UE positioning capabilityinformation, UE service area information, and/or UE velocityinformation. These processes may be similar to the processes describedabove with respect to FIG. 22 . For brevity, further description willnot be repeated here.

In response to the message received from the (R)AN, the LMC/LMF may senda message (e.g. (R)AN capability notification) to a network function(e.g. a UDM, OAM), the (R)AN capability notification message maycomprise one or more parameters of the Positioning Capability Reportmessage (e.g. (R)AN positioning capability information, UE positioningcapability information, UE service area information, and/or UE velocityinformation). In an example, the LMC/LMF may receive (R)AN positioningcapability information of one or more base stations from the one or morebase stations in a registration area of the wireless device. The LMC/LMFmay send the (R)AN positioning capability information of one or morebase stations to the network function.

In an example, a (R)AN may send to the AMF a message (e.g. an N2message), the N2 message may comprise at least one of: N2 parameters, aRegistration Request message, (R)AN positioning capability information,UE positioning capability information, UE service area information,and/or UE velocity information. For example, the N2 parameters maycomprise a selected PLMN ID (or PLMN ID and NID), Location Informationand Cell Identity related to the cell in which the UE is camping, UEContext Request which may indicate that a UE context including securityinformation needs to be setup at the NG-RAN. For example, the N2parameters may comprise an Establishment cause, a CAG Identifier if theUE is accessing the NG-RAN using a CAG cell and IAB-Indication if theindication is received in AN parameters from the UE. For example, theRegistration Request message may comprise at least one of: aRegistration type, a UE identity (e.g. SUCI, 5G-GUTI or PEI), lastvisited TAI (if available), Security parameters, Requested NSSAI,Mapping Of Requested NSSAI, Default Configured NSSAI Indication, UERadio Capability Update, UE MM Core Network Capability, PDU Sessionstatus, List Of PDU Sessions To Be Activated, Follow-on request, MICOmode preference, Requested Active Time, Requested DRX parameters,extended idle mode DRX parameters, LADN DNN(s) or Indicator OfRequesting LADN Information, NAS message container, Support forrestriction of use of Enhanced Coverage, Preferred Network Behaviour, UEPolicy Container (e.g. list of PSIs, indication of UE support for ANDSPand the operating system identifier) and/or UE Radio Capability ID.

In response to the message received from the (R)AN, the AMF may send amessage (e.g. (R)AN capability notification) to a network function (e.g.a UDM, OAM), the (R)AN capability notification message may comprise oneor more parameters of the N2 message (e.g. (R)AN positioning capabilityinformation, UE positioning capability information, UE service areainformation, and/or UE velocity information). In an example, the AMF mayreceive (R)AN positioning capability information of one or more basestations from the one or more base stations in a registration area ofthe wireless device. The AMF may send the (R)AN positioning capabilityinformation of the one or more base stations to the network function.

In an example, a gateway mobile location center (GMLC) may receive amessage (e.g. Positioning Information Request) from a network functionand/or a UE. The network function may be a location services (LCS)client, an NEF, an AF, and/or a (R)AN. The Positioning InformationRequest message may indicate requesting/querying positioning informationof the UE (e.g., the UE illustrated in the figure). The PositioningInformation Request message may comprise one or more informationelements/parameters. For example, the Positioning Information Requestmessage may comprise one or more positioning information requestparameters indicating one or more of the following: a UE identity of theUE for which position information is requested (e.g. GPSI and/or SUPI),a parameter indicating whether the request is assured, a parameterindicating requested positioning service level, a parameter indicatingrequested positioning service area, a parameter indicating requestedenhanced positioning service area, a required QoS, Supported GAD shapes,and/or an LCS client type. The parameter indicating whether the requestis assured may comprise a least one value: assured, or not assured. Thevalue assured may indicate that the requested parameters (e.g. requestedpositioning service level) in the message should be guaranteed, e.g.,the GMLC may reject the request if the GMLC cannot guaranteed therequest. The value not assured may indicate that the requestedparameters (e.g. requested positioning service level) in the message maynot be guaranteed, e.g., the GMLC may provide a different parameterscompare to the requested parameters. The requested positioning servicelevel may indicate a positioning service level expected by the networkfunction and/or the UE. The requested positioning service area mayindicate a positioning service area expected by the network functionand/or the UE. The requested enhanced positioning service area mayindicate an enhanced positioning service area expected by the networkfunction and/or the UE.

In an example, the requested capability of positioning service level mayindicate a requested positioning service level. In an example, therequested capability of positioning service level may comprise at leastone of: a parameter indicating requested positioning service levelnumber (e.g. 1, 2, . . . 7); a parameter indicating an requestedabsolute or relative positioning; a parameter indicating a requestedhorizontal accuracy; a parameter indicating a requested verticalaccuracy; a parameter indicating a requested positioning serviceavailability; a parameter indicating a requested positioning servicelatency; a parameter indicating a requested 5G positioning service area;and/or a parameter indicating a requested 5G enhanced positioningservice area. In an example, the requested positioning service area mayindicate coverage, environment of use and/or UE velocity. For example,the requested positioning service area may indicate requested indoorand/or outdoor coverage. For example, the requested positioning servicearea may indicate requested UE speed in the indoor and/or outdoorcoverage. For example, the requested enhanced positioning service areamay indicate supported indoor and/or outdoor coverage. For example, therequested enhanced positioning service area may indicate requested UEspeed in the indoor and/or outdoor coverage. FIG. 21 shows exampledefinition of requested capability of positioning service level,requested positioning service area, and/or requested enhancedpositioning service area. In FIG. 21 , Positioning service level is anexample of requested capability of positioning service level, 5Gpositioning service area is an example of requested positioning servicearea, 5G enhanced positioning service area is an example of requestedenhanced positioning service area. In an example, the required QoS maycomprise at least one of: accuracy of the positioning, response time forthe positioning request, LCS QoS class. In an example, the LCS clienttype may comprise at least one of: emergency services, value addedservices, PLMN operator services, and/or lawful intercept services.

In response to the message received, the GMLC may send a message (e.g.Nudm_UECM_Get Request, Positioning Capability Query) to a networkfunction. The network function may be an AMF, a UDM, and/or an OAM. Forexample, the GMLC may send a Nudm_UECM_Get Request message to a (home)UDM of the UE. The Nudm_UECM_Get Request message may comprise the one ormore information elements/parameters of the Positioning InformationRequest message described above, for example, the UE identity. In anexample, the Nudm_UECM_Get Request message may comprise a parameterindicating requesting/querying (R)AN positioning capability. In anexample, the Nudm_UECM_Get Request message may comprise a parameterindicating requesting/querying UE positioning capability.

In response to the message received from the GMLC, the UDM may send aresponse message (e.g. Nudm_UECM_Get Response) to the GMLC, theNudm_UECM_Get Response message may comprise at least one of: (R)ANpositioning capability information of the at least one base station, UEpositioning capability information, UE service area information, and/orUE velocity information. In an example, based on local configuration,the Nudm_UECM_Get Response message may comprise at least one of: aparameter indicating supported positioning service level for the UEand/or PLMN; a parameter indicating supported positioning service area,and/or a parameter indicating the supported enhanced positioning servicearea.

In response to the message received from the UDM, the GMLC may take oneor more actions. In an example action, based on the message receivedfrom the LCS client and/or the message received from the UDM, the GMLCmay determine at least one of: accepted positioning service level forthe UE and/or the PLMN, accepted positioning service area for the UEand/or the PLMN, and/or accepted enhanced positioning service area forthe UE and/or the PLMN. For example, based on the requested positioningservice level, the requested positioning service area, the requestedenhanced positioning service area, the required QoS, (R)AN positioningcapability information of the at least one base station, the UEpositioning capability information, the UE service area information,and/or the UE velocity information, the GMLC may determine at least oneof: accepted/supported positioning service level, accepted/supportedpositioning service area, and/or accepted/supported enhanced positioningservice area.

In an example, the accepted/supported positioning service level mayindicate an accepted/supported positioning service level. In an example,the accepted/supported positioning service level may comprise at leastone of: a parameter indicating accepted/supported service level number(e.g. 1, 2, . . . 7); a parameter indicating an accepted/supportedabsolute or relative positioning; a parameter indicating anaccepted/supported horizontal accuracy; a parameter indicating anaccepted/supported vertical accuracy; a parameter indicating anaccepted/supported positioning service availability; a parameterindicating an accepted/supported positioning service latency; aparameter indicating an accepted/supported 5G positioning service area;and/or a parameter indicating an accepted/supported 5G enhancedpositioning service area. In an example, the accepted/supportedpositioning service area may indicate coverage, environment of useand/or UE velocity. For example, the accepted/supported positioningservice area may indicate supported indoor and/or outdoor coverage. Forexample, the accepted/supported positioning service area may indicatesupported UE speed in the indoor and/or outdoor coverage. For example,the accepted/supported enhanced positioning service area may indicatesupported indoor and/or outdoor coverage. For example, theaccepted/supported enhanced positioning service area may indicatesupported UE speed in the indoor and/or outdoor coverage. In an example,the accepted/supported positioning service level may be usedindependently. In an example, the accepted/supported positioning servicelevel may be used with the accepted/supported positioning service areaand/or the accepted/supported enhanced positioning service areatogether.

FIG. 21 shows example of accepted/supported positioning service level,supported positioning service area, and/or supported enhancedpositioning service area. In FIG. 21 , Positioning service level is anexample of accepted/supported capability of positioning service level,5G positioning service area is an example of accepted/supportedpositioning service area, 5G enhanced positioning service area is anexample of accepted/supported enhanced positioning service area.

In an example, the requested positioning service level may indicate arequested service level (number) 2 and/or a requested horizontalaccuracy of 3 meters, the requested positioning service area mayindicate an outdoor environment with a UE speed of 500 km/h, therequested enhanced positioning service area may indicate an indoorenvironment with a UE speed of 30 km/h, the (R)AN positioning capabilityinformation of the at least one base station may indicate that the (R)ANsupports ECID (capability and/or positioning method), the UE positioningcapability information may indicate that the UE supports ECID(capability and/or positioning method) and/or OTDOA (capability and/orpositioning method), the UE service area information may indicate UE isin an indoor area, the UE velocity information may indicate the speed ofUE is 30 km/h, based on above information, the GMLC may determine atleast one of: an accepted/supported positioning service level (number) 1for the UE and/or the PLMN; an accepted/supported positioning servicearea where UE may have a speed up to 30 km/h for indoor environment, andup to 250 km/h for outdoor (rural and urban) environment; and/or anaccepted/supported enhanced positioning service area where UE may have aspeed up to 30 km/h for indoor environment. As shown in FIG. 21 , the anaccepted/supported positioning service level 1 may have a horizontalaccuracy of 10 meters.

In an example, the requested positioning service level may indicate arequested service level (number) 2 and/or a requested horizontalaccuracy of 3 meters, the requested positioning service area mayindicate an outdoor environment with a UE speed of 500 km/h, the (R)ANpositioning capability information of the at least one base station mayindicate that the (R)AN supports ECID and/or OTDOA, the UE positioningcapability information may indicate that the UE supports ECID, OTDOA,WLAN positioning, and/or Bluetooth positioning, the UE service areainformation may indicate UE is in an outdoor area, the UE velocityinformation may indicate the speed of UE is 300 km/h, based on aboveinformation, the GMLC may determine at least one of: anaccepted/supported positioning service level 2 for the UE and/or thePLMN; an accepted/supported positioning service area where UE may have aspeed up to 500 km/h for outdoor environment. As shown in FIG. 21 , theaccepted/supported positioning service level 2 may have a horizontalaccuracy of 3 meters and a vertical accuracy of 3 meters.

In an example, the requested positioning service level may indicate arequested service level (number) 7 and/or a requested vertical accuracyof 0.2 meters, the requested positioning service area may indicate anoutdoor environment with a UE speed of 30 km/h, the requested enhancedpositioning service area may indicate an indoor environment with a UEspeed of 30 km/h, the (R)AN positioning capability information of the atleast one base station may indicate that the (R)AN supports ECID and/orOTDOA, the UE positioning capability information may indicate that theUE supports ECID, OTDOA, WLAN positioning, and/or high accuracy (HA)GNSS (e.g. Real-time kinematic (RTK) positioning), the UE service areainformation may indicate UE is in an indoor area, the UE velocityinformation may indicate the speed of UE is 30 km/h, based on aboveinformation, the GMLC may determine at least one of: anaccepted/supported positioning service level 7 for the UE and/or thePLMN; an accepted/supported positioning service area where UE may have aspeed up to 30 km/h for indoor and outdoor environment; and/or anaccepted/supported enhanced positioning service area where UE may have aspeed up to 30 km/h for indoor and outdoor environment. As shown in FIG.21 , the supported capability of positioning service level 7 may have ahorizontal accuracy of 0.2 meters and a vertical accuracy of 0.2 meters.

In an example action, in response to the message received from the LCSclient, the GMLC may send to the LCS client a response message (e.g.Positioning Information Response). The Positioning Information Responsemessage may comprise a cause value indicating whether the requestedpositioning service level is accepted or not. The PositioningInformation Response message may comprise the accepted/supportedpositioning service level, the accepted/supported positioning servicearea, and/or the accepted/supported enhanced positioning service area.In response to the message received from the GMLC, based on theaccepted/supported positioning service level, accepted/supportedpositioning service area, and/or accepted/supported enhanced positioningservice area, the LCS client may determine one or more requestedparameters for a positioning request message. For example, thedetermined one or more requested parameters may equal to the supportedcapability of positioning service level, the supported positioningservice area, and/or the supported enhanced positioning service area.For example, the determined one or more requested parameters maydifferent from (e.g. less than) the supported capability of positioningservice level, the supported positioning service area, and/or thesupported enhanced positioning service area. For example, the determinedone or more requested parameters may comprise at least one of: arequested positioning service level, a requested positioning servicearea, a requested enhanced positioning service area, a requestedhorizontal positioning accuracy, a requested vertical positioningaccuracy, and/or a requested QoS. In an example action, the LCS clientmay send to the GMLC a message (e.g. positioning request message). Thepositioning request message may indicate requesting positioninginformation of the UE. The positioning request message may comprise thedetermined one or more requested parameters.

In an example action, in response to the message received from the LCSclient and/or in response to the determining, the GMLC may send amessage (e.g. Positioning Information Request) to the AMF, thePositioning Information Request may comprise at least one of: the UEidentity, the required QoS, the Supported GAD shapes, the LCS clienttype, the accepted/supported positioning service level, theaccepted/supported positioning service area, and/or theaccepted/supported enhanced positioning service area. In response to themessage received from the GMLC, the AMF may send a message (e.g.Positioning Information Request) to the LMC/LMF, the message maycomprise one or more information elements/parameters received from theGMLC (e.g. received by the Positioning Information Request message).

In response to the message received from the AMF, the LMC/LMF may takeone or more actions. In an example action, based on the one or moreinformation elements/parameters received from the AMF, the (R)ANpositioning capability, the UE positioning capability, the UE servicearea information, and/or the UE velocity information, the LMC/LMF maydetermine one or more positioning methods for the positioning request.For example, based on the accepted/supported positioning service level,the accepted/supported positioning service area, the accepted/supportedenhanced positioning service area, the required QoS, the (R)ANpositioning capability, the UE positioning capability, the UE servicearea information, and/or the UE velocity information, the LMC/LMF maydetermine one or more positioning methods for the positioning request.

In an example, the accepted/supported positioning service level mayindicate a accepted/supported service level (number) 1 and/or aaccepted/supported horizontal accuracy of 10 meters, theaccepted/supported positioning service area may indicate an outdoorenvironment with a UE speed of 250 km/h, the requested enhancedpositioning service area may indicate an indoor environment with a UEspeed of 30 km/h, the (R)AN positioning capability information of the atleast one base station may indicate that the (R)AN supports ECID(capability and/or positioning method), the UE positioning capabilityinformation may indicate that the UE supports ECID (capability and/orpositioning method) and/or OTDOA (capability and/or positioning method),the UE service area information may indicate UE is in an indoor area,the UE velocity information may indicate the speed of UE is 30 km/h,and/or the required QoS may indicate a vertical accuracy 3 meters, basedon above information, the LMC/LMF may determine a positioning method ofECID.

In an example, the accepted/supported positioning service level mayindicate a accepted/supported service level (number) 7 and/or aaccepted/supported vertical accuracy of 0.2 meters, theaccepted/supported positioning service area may indicate an outdoorenvironment with a UE speed of 30 km/h, the accepted/supported enhancedpositioning service area may indicate an indoor environment with a UEspeed of 30 km/h, the (R)AN positioning capability information of the atleast one base station may indicate that the (R)AN supports ECID and/orOTDOA, the UE positioning capability information may indicate that theUE supports ECID, OTDOA, WLAN positioning, and/or high accuracy (HA)GNSS (e.g. Real-time kinematic (RTK) positioning), the UE service areainformation may indicate UE is in an indoor area, the UE velocityinformation may indicate the speed of UE is 30 km/h, and/or the requiredQoS may indicate a horizontal accuracy 0.3 meters, based on aboveinformation, the LMC/LMF may determine that a combination of more thanone positioning method may meet the requested positioning accuracy, forexample, the LMC/LMF may determine the OTDOA positioning method and/orthe HA GNSS positioning method.

In response to the determining, the LMC/LMF may send a message (e.g.Positioning Information Request) to the UE. For example, LPP may be usedfor the positioning signaling between an LMC/LMF and the UE. ThePositioning Information Request message may comprise at least oneinformation element/parameter: the determined one or more positioningmethods, the UE identity, the required QoS, the Supported GAD shapes,and/or the LCS client type. In an example, the LMC/LMF may send amessage (e.g. Positioning Information Request) to the (R)AN comprisingthe at least one information element/parameter.

In response to the message received from the LMC/LMF, the UE and/or the(R)AN may perform positioning measurement, and report the measurementresults to the LMC/LMF, the LMC/LMF may determine UE positioninginformation based on the measurement results. The LMC/LMF may send tothe AMF a response message (e.g. Positioning Information Response)comprising the UE positioning information. The AMF may send to the GMLCa response message (e.g. Positioning Information Response) comprisingthe UE positioning information. The GMLC may send to the LCS client aresponse message (e.g. Positioning Information Response) comprising theUE positioning information.

FIG. 31 shows an example call flow which may comprise one or moreactions. In an example, a UE may send a message (e.g. a LPP message, forexample, a ProvideCapabilities message)) to an LMC/LMF, theProvideCapabilities message may comprise at least one of: UE positioningcapability information, UE service area information, and/or UE velocityinformation. These processes may be similar to the processes describedabove with respect to FIG. 22 . For brevity, further description willnot be repeated here.

In response to the message received from the UE, the LMC/LMF may send amessage (e.g. UE capability notification) to a network function (e.g. aUDM, OAM), the UE capability notification message may comprise one ormore parameters of the ProvideCapabilities message (e.g. UE positioningcapability information, UE service area information, and/or UE velocityinformation).

In an example, the UE may send a message (e.g. a NAS message, forexample, a REGISTRATION REQUEST message)) to an AMF, the REGISTRATIONREQUEST message may comprise at least one of: UE positioning capabilityinformation, UE service area information, and/or UE velocityinformation. In response to the message received from the UE, the AMFmay send a message (e.g. UE capability notification) to a networkfunction (e.g. a UDM, OAM), the UE capability notification message maycomprise one or more parameters of the REGISTRATION REQUEST message(e.g. UE positioning capability information, UE service areainformation, and/or UE velocity information).

In an example, a (R)AN may send to the LMC/LMF a message (e.g. a NRPPamessage, for example, a Positioning Capability Report message), thePositioning Capability Report message may comprise at least one of:(R)AN positioning capability information, UE positioning capabilityinformation, UE service area information, and/or UE velocityinformation. These processes may be similar to the processes describedabove with respect to FIG. 22 . For brevity, further description willnot be repeated here.

In response to the message received from the (R)AN, the LMC/LMF may senda message (e.g. (R)AN capability notification) to a network function(e.g. a UDM, OAM), the (R)AN capability notification message maycomprise one or more parameters of the Positioning Capability Reportmessage (e.g. (R)AN positioning capability information, UE positioningcapability information, UE service area information, and/or UE velocityinformation). In an example, the LMC/LMF may receive (R)AN positioningcapability information of one or more base stations from the one or morebase stations in a registration area of the wireless device. The LMC/LMFmay send the (R)AN positioning capability information of one or morebase stations to the network function.

In an example, a (R)AN may send to the AMF a message (e.g. an N2message), the N2 message may comprise at least one of: N2 parameters, aRegistration Request message, (R)AN positioning capability information,UE positioning capability information, UE service area information,and/or UE velocity information. These processes may be similar to theprocesses described above with respect to FIG. 30 . For brevity, furtherdescription will not be repeated here.

In response to the message received from the (R)AN, the AMF may send amessage (e.g. (R)AN capability notification) to a network function (e.g.a UDM, OAM), the (R)AN capability notification message may comprise oneor more parameters of the N2 message (e.g. (R)AN positioning capabilityinformation, UE positioning capability information, UE service areainformation, and/or UE velocity information). In an example, the AMF mayreceive (R)AN positioning capability information of one or more basestations from the one or more base stations in a registration area ofthe wireless device. The AMF may send the (R)AN positioning capabilityinformation of the one or more base stations to the network function.

In an example, a NEF may receive a message (e.g. Positioning InformationRequest) from an AF. The Positioning Information Request message mayindicate requesting/querying positioning information of the UE (e.g.,the UE illustrated in the figure). The Positioning Information Requestmessage may comprise one or more information elements/parameters. Forexample, the Positioning Information Request message may comprise one ormore positioning information request parameters indicating one or moreof the following: a UE identity of the UE for which position informationis requested (e.g. GPSI and/or SUPI), a parameter indicating requestedpositioning service level, a parameter indicating requested positioningservice area, a parameter indicating requested enhanced positioningservice area, a required QoS, Supported GAD shapes, and/or an LCS clienttype. The requested positioning service level may indicate a positioningservice level expected by the network function and/or the UE. Therequested positioning service area may indicate a positioning servicearea expected by the network function and/or the UE. The requestedenhanced positioning service area may indicate an enhanced positioningservice area expected by the network function and/or the UE.

In an example, the requested capability of positioning service level mayindicate a requested positioning service level. In an example, therequested capability of positioning service level may comprise at leastone parameter as described above with respect to FIG. 30 . For brevity,further description will not be repeated here.

In response to the message received, the NEF may send a message (e.g.Nudm_UECM_Get Request, Positioning Capability Query) to a networkfunction. The network function may be an AMF, a UDM, and/or an OAM. Forexample, the NEF may send a Nudm_UECM_Get Request message to a (home)UDM of the UE. The Nudm_UECM_Get Request message may comprise the one ormore information elements/parameters of the Positioning InformationRequest message described above, for example, the UE identity. In anexample, the Nudm_UECM_Get Request message may comprise a parameterindicating requesting/querying (R)AN positioning capability. In anexample, the Nudm_UECM_Get Request message may comprise a parameterindicating requesting/querying UE positioning capability.

In response to the message received from the GMLC, the UDM may send aresponse message (e.g. Nudm_UECM_Get Response) to the GMLC, theNudm_UECM_Get Response message may comprise at least one of: (R)ANpositioning capability information of the at least one base station, UEpositioning capability information, UE service area information, and/orUE velocity information. In an example, based on local configuration,the Nudm_UECM_Get Response message may comprise at least one of: aparameter indicating supported positioning service level for the UEand/or PLMN; a parameter indicating supported positioning service area,and/or a parameter indicating the supported enhanced positioning servicearea.

In response to the message received from the UDM, the NEF may take oneor more actions. In an example action, based on the message receivedfrom the AF and/or the message received from the UDM, the NEF maydetermine at least one of: accepted positioning service level for the UEand/or the PLMN, accepted positioning service area for the UE and/or thePLMN, and/or accepted enhanced positioning service area for the UEand/or the PLMN. For example, based on the requested positioning servicelevel, the requested positioning service area, the requested enhancedpositioning service area, the required QoS, (R)AN positioning capabilityinformation of the at least one base station, the UE positioningcapability information, the UE service area information, and/or the UEvelocity information, the NEF may determine at least one of:accepted/supported positioning service level, accepted/supportedpositioning service area, and/or accepted/supported enhanced positioningservice area. These processes may be similar to the processes of GMLCdescribed above with respect to FIG. 30 . For brevity, furtherdescription will not be repeated here.

In an example action, in response to the message received from the AF,the NEF may send to the AF a response message (e.g. PositioningInformation Response). The Positioning Information Response message maycomprise the accepted/supported positioning service level, theaccepted/supported positioning service area, and/or theaccepted/supported enhanced positioning service area. In response to themessage received from the NEF, based on the accepted/supportedpositioning service level, accepted/supported positioning service area,and/or accepted/supported enhanced positioning service area, the AF maydetermine one or more requested parameters for a positioning requestmessage. For example, the determined one or more requested parametersmay equal to the supported capability of positioning service level, thesupported positioning service area, and/or the supported enhancedpositioning service area. For example, the determined one or morerequested parameters may different from (e.g. less than) the supportedcapability of positioning service level, the supported positioningservice area, and/or the supported enhanced positioning service area.For example, the determined one or more requested parameters maycomprise at least one of: a requested positioning service level, arequested positioning service area, a requested enhanced positioningservice area, a requested horizontal positioning accuracy, a requestedvertical positioning accuracy, and/or a requested QoS. In an exampleaction, the AF may send to the NEF a message (e.g. positioning requestmessage). The positioning request message may indicate requestingpositioning information of the UE. The positioning request message maycomprise the determined one or more requested parameters.

In an example action, in response to the message received from the AFand/or in response to the determining, the NEF may send a message (e.g.Positioning Information Request) to the GMLC, the PositioningInformation Request may comprise at least one of: the UE identity, therequired QoS, the Supported GAD shapes, the LCS client type, theaccepted/supported positioning service level, the accepted/supportedpositioning service area, and/or the accepted/supported enhancedpositioning service area. In response to the message received from theNEF, the GMLC may send to the AMF a message (e.g. PositioningInformation Request) comprising one or more informationelements/parameters received from the NEF. In response to the messagereceived from the GMLC, the AMF may send a message (e.g. PositioningInformation Request) to the LMC/LMF, the message may comprise one ormore information elements/parameters received from the GMLC (e.g.received by the Positioning Information Request message).

In response to the message received from the AMF, the LMC/LMF may takeone or more actions. In an example action, based on the one or moreinformation elements/parameters received from the AMF, the (R)ANpositioning capability, the UE positioning capability, the UE servicearea information, and/or the UE velocity information, the LMC/LMF maydetermine one or more positioning methods for the positioning request.For example, based on the accepted/supported positioning service level,the accepted/supported positioning service area, the accepted/supportedenhanced positioning service area, the required QoS, the (R)ANpositioning capability, the UE positioning capability, the UE servicearea information, and/or the UE velocity information, the LMC/LMF maydetermine one or more positioning methods for the positioning request.These processes may be similar to the processes described above withrespect to FIG. 30 . For brevity, further description will not berepeated here.

In response to the determining, the LMC/LMF may send a message (e.g.Positioning Information Request) to the UE. For example, LPP may be usedfor the positioning signaling between an LMC/LMF and the UE. ThePositioning Information Request message may comprise at least oneinformation element/parameter: the determined one or more positioningmethods, the UE identity, the required QoS, the Supported GAD shapes,and/or the LCS client type. In an example, the LMC/LMF may send amessage (e.g. Positioning Information Request) to the (R)AN comprisingthe at least one information element/parameter.

In response to the message received from the LMC/LMF, the UE and/or the(R)AN may perform positioning measurement, and report the measurementresults to the LMC/LMF, the LMC/LMF may determine UE positioninginformation based on the measurement results. The LMC/LMF may send tothe AMF a response message (e.g. Positioning Information Response)comprising the UE positioning information. The AMF may send to the GMLCa response message (e.g. Positioning Information Response) comprisingthe UE positioning information. The GMLC may send to the NEF a responsemessage (e.g. Positioning Information Response) comprising the UEpositioning information. The NEF may send to the AF a response message(e.g. Positioning Information Response) comprising the UE positioninginformation.

In an example, a gateway mobile location center (GMLC) may receive froma location services (LCS) client, a first message requesting capabilityof positioning service level for a wireless device. In an example, theGMLC may receive from a network function, a second message indicating atleast one of: positioning capability of the wireless device; orpositioning capability of at least one base station. In an example, theGMLC may determine the capability of positioning service level based onthe second message. In an example, the GMLC may send to the LCS client,a response message to the first message, wherein the response messagemay comprise the capability of positioning service level.

In an example embodiment, the at least one base station may be in aregistration area of the wireless device. In an example embodiment, theat least one base station may be plural base stations inside aregistration area of the wireless device. In an example embodiment, thesecond message may further comprise service area information of thewireless device. In an example embodiment, the second message mayfurther comprise velocity information of the wireless device. In anexample embodiment, the determine may further bases on service areainformation of the wireless device. In an example embodiment, thedetermine may further base on velocity information of the wirelessdevice. In an example embodiment, the capability of positioning servicelevel may indicate a supported positioning service level. In an exampleembodiment, the capability of positioning service level may comprise apositioning service level number. In an example embodiment, thecapability of positioning service level may comprise a parameterindicating an absolute or a relative positioning. In an exampleembodiment, the capability of positioning service level may comprise aparameter indicating a horizontal accuracy. In an example embodiment,the capability of positioning service level may comprise a parameterindicating a vertical accuracy. In an example embodiment, the capabilityof positioning service level may comprise a parameter indicating apositioning service availability. In an example embodiment, thecapability of positioning service level may comprise a parameterindicating a positioning service latency. In an example embodiment, thecapability of positioning service level may comprise a parameterindicating a 5G positioning service area. In an example embodiment, thecapability of positioning service level may comprise a parameterindicating a 5G enhanced positioning service area.

In an example embodiment, the network function may comprise at least oneof: an access and mobility management function (AMF); a unified datamanagement (UDM); or an operations administration and management (OAM).In an example embodiment, the positioning capability of the wirelessdevice positioning capability may comprise at least one of: supportingEnhanced Cell Identity (ECID) capability; supporting Observed TimeDifference of Arrival (OTDOA) capability; supporting network-assistedGNSS methods; supporting WLAN positioning; supporting Bluetoothpositioning; supporting Terrestrial Beacon System (TBS) positioning;supporting barometric pressure sensor positioning; or no support of apositioning capability. In an example embodiment, the positioningcapability of at least one base station comprises at least one of:supporting Enhanced Cell Identity (ECID) capability; supporting ObservedTime Difference of Arrival (OTDOA) capability; supporting uplinkrelative time of arrival; supporting uplink reference signal receivedpower measurements; supporting uplink Angle of Arrival (UL AoA)measurements; supporting multiple RTT positioning; supporting gNB RX-TXtime difference measurements; or no support of a positioning capability.In an example embodiment, the first message and the response message mayfurther comprise an identifier of the wireless device.

In an example, an access and mobility management function (AMF) mayreceive from a gateway mobile location center (GMLC), a first messagerequesting capability of positioning service level for a public landmobile network (PLMN) and a wireless device. In an example, the AMF mayreceive from a network function, a second message indicating:positioning capability of the wireless device; and positioningcapability of a base station, wherein the wireless device accesses thePLMN via the base station. In an example, based on the second message,the AMF may determine, the capability of positioning service level. Inan example, the AMF may send to the GMLC, a response message to thefirst message, wherein the response message may comprise the capabilityof positioning service level. In an example embodiment, the networkfunction may comprise at least one of: a location management function; alocation management component; a unified data management (UDM); or anoperations administration and management (OAM).

In an example, a location management component (LMC) may receive from anaccess and mobility management function (AMF), a first messagerequesting capability of positioning service level for a public landmobile network (PLMN) and a wireless device. In an example, the LMC mayreceive from a network function, a second message indicating:positioning capability of the wireless device; and positioningcapability of a base station, wherein the wireless device accesses thePLMN via the base station. In an example, the LMC may determine thecapability of positioning service level based on the second message. TheLMC may send to the AMF a response message to the first message, whereinthe response message may comprise the capability of positioning servicelevel.

In an example, a gateway mobile location center (GMLC) may receive froma location services (LCS) client, a first message comprising a requestedpositioning service level for a wireless device. In an example, the GMLCmay receive from a network function, at least one second messageindicating at least one of: positioning capability of the wirelessdevice; or positioning capability of at least one base station. In anexample, the GMLC may determine an accepted positioning service levelbased on the at least one second message. In an example, the GMLC maysend to the LCS client, a response message indicating at least one of:whether the requested positioning service level is accepted or not; orthe accepted positioning service level. In an example, the determiningmay be further based on the first message. In an example, the GMLC maysend to an access and mobility management function (AMF), a positioningrequest message comprising the accepted positioning service level. In anexample, the first message may further comprise a parameter indicatingwhether the request is assured.

In an example, a location management component (LMC) may receive from anaccess and mobility management function (AMF), a first messagecomprising an accepted positioning service level for a wireless device.In an example, the LMC may receive from a network function, a secondmessage indicating: positioning capability of the wireless device; andpositioning capability of a base station, wherein the wireless deviceregisters to the base station. In an example, based on the acceptedpositioning service level and the second message, the LMC may determinea positioning method for the wireless device. In an example, the LMC maysend to the wireless device the positioning method.

In an example, a network exposure function (NEF) may receive from anapplication function (AF), a first message comprising a requestedpositioning service level for a wireless device. In an example, the NEFmay receive from a network function, a second message indicating:positioning capability of the wireless device; and positioningcapability of a base station, wherein the wireless device registers tothe base station. In an example, based on the requested positioningservice level and the second message, the NEF may determine an acceptedpositioning service level. In an example, the NEF may send to a gatewaymobile location center (GMLC), a positioning request message comprisingthe accepted positioning service level.

According to various embodiments, one or more devices such as, forexample, a wireless device, off-network wireless device, a base station,a core network device, and/or the like, may be employed in a system. Oneor more of the devices may be configured to perform particularoperations or actions by virtue of having software, firmware, hardware,or a combination of them installed on the one or more of the devices,that in operation causes or cause the one or more devices to perform theactions. One or more computer programs can be configured to performparticular operations or actions by virtue of including instructionsthat, when executed by data processing apparatus, cause the apparatus toperform the actions. Embodiments of example actions are illustrated inthe accompanying figures and specification. Features from variousembodiments may be combined to create yet further embodiments.

In this specification, “a” and “an” and similar phrases are to beinterpreted as “at least one” and “one or more.” In this specification,the term “may” is to be interpreted as “may, for example.” In otherwords, the term “may” is indicative that the phrase following the term“may” is an example of one of a multitude of suitable possibilities thatmay, or may not, be employed to one or more of the various Examples. IfA and B are sets and every element of A is an element of B, A is calleda subset of B. In this specification, only non-empty sets and subsetsare considered. For example, possible subsets of B={cell1, cell2} are:{cell1}, {cell2}, and {can, cell2}.

In this specification, various Examples are disclosed. Limitations,features, and/or elements from the disclosed example Examples may becombined to create further Examples within the scope of the disclosure.

In this specification, various Examples are disclosed. Limitations,features, and/or elements from the disclosed example Examples may becombined to create further Examples within the scope of the disclosure.

In this specification, parameters (Information elements: IEs) maycomprise one or more objects, and one of those objects may comprise oneor more other objects. For example, if parameter (IE) N comprisesparameter (IE) M, and parameter (IE) M comprises parameter (IE) K, andparameter (IE) K comprises parameter (information element) J, then, forexample, N comprises K, and N comprises J. In an example, when one ormore messages comprise a plurality of parameters, it implies that aparameter in the plurality of parameters is in at least one of the oneor more messages, but does not have to be in one of the one or moremessages.

Many of the elements described in the disclosed Examples may beimplemented as modules. A module is defined here as an isolatableelement that performs a defined function and has a defined interface toother elements. The modules described in this disclosure may beimplemented in hardware, software in combination with hardware,firmware, wetware (e.g. hardware with a biological element) or acombination thereof, some of which are behaviorally equivalent. Forexample, modules may be implemented as a software routine written in acomputer language configured to be executed by a hardware machine (suchas C, C++, Fortran, Java, Basic, Matlab or the like) or amodeling/simulation program such as Simulink, Stateflow, GNU Octave, orLabVIEWMathScript. Additionally, it may be possible to implement modulesusing physical hardware that incorporates discrete or programmableanalog, digital and/or quantum hardware. Examples of programmablehardware comprise: computers, microcontrollers, microprocessors,application-specific integrated circuits (ASICs); field programmablegate arrays (FPGAs); and complex programmable logic devices (CPLDs).Computers, microcontrollers and microprocessors are programmed usinglanguages such as assembly, C, C++ or the like. FPGAs, ASICs and CPLDsare often programmed using hardware description languages (HDL) such asVHSIC hardware description language (VHDL) or Verilog that configureconnections between internal hardware modules with lesser functionalityon a programmable device. Finally, it needs to be emphasized that theabove mentioned technologies are often used in combination to achievethe result of a functional module.

The disclosure of this patent document incorporates material which issubject to copyright protection. The copyright owner has no objection tothe facsimile reproduction by anyone of the patent document or thepatent disclosure, as it appears in the Patent and Trademark Officepatent file or records, for the limited purposes required by law, butotherwise reserves all copyright rights whatsoever.

While various Examples have been described above, it should beunderstood that they have been presented by way of example, and notlimitation. It will be apparent to persons skilled in the relevantart(s) that various changes in form and detail can be made thereinwithout departing from the spirit and scope. In fact, after reading theabove description, it will be apparent to one skilled in the relevantart(s) how to implement alternative Examples. Thus, the present Examplesshould not be limited by any of the above described exemplary Examples.In particular, it should be noted that, for example purposes, the aboveexplanation has focused on the example(s) using 5G AN. However, oneskilled in the art will recognize that Examples of the invention may beimplemented in a system comprising one or more legacy systems or LTE.The disclosed methods and systems may be implemented in wireless orwireline systems. The features of various Examples presented in thisinvention may be combined. One or many features (method or system) ofone Example may be implemented in other Examples. A limited number ofexample combinations are shown to indicate to one skilled in the art thepossibility of features that may be combined in various Examples tocreate enhanced transmission and reception systems and methods.

In addition, it should be understood that any figures which highlightthe functionality and advantages, are presented for example purposes.The disclosed architecture is sufficiently flexible and configurable,such that it may be utilized in ways other than that shown. For example,the actions listed in any flowchart may be re-ordered or optionally usedin some examples.

Further, the purpose of the Abstract of the Disclosure is to enable theU.S. Patent and Trademark Office and the public generally, andespecially the scientists, engineers and practitioners in the art whoare not familiar with patent or legal terms or phraseology, to determinequickly from a cursory inspection the nature and essence of thetechnical disclosure of the application. The Abstract of the Disclosureis not intended to be limiting as to the scope in any way.

Finally, it is the applicant's intent that only claims that include theexpress language “means for” or “step for” be interpreted under 35U.S.C. 112. Claims that do not expressly include the phrase “means for”or “step for” are not to be interpreted under 35 U.S.C. 112.

What is claimed is:
 1. A gateway mobile location center (GMLC),comprising: one or more processors; and memory storing instructionsthat, when executed by the one or more processors, cause the GMLC toperform operations comprising: receiving, from a location services (LCS)client, a request for a capability of a positioning service level for awireless device; receiving, from a network function, a second messageindicating at least one of: a positioning capability of the wirelessdevice; and a positioning capability of at least one base station;determining the capability of the positioning service level for thewireless device, based on the second message; and sending, by the GMLCto the LCS client, a response comprising the capability of thepositioning service level, wherein the capability of the positioningservice level comprises a parameter indicating an absolute or a relativepositioning.
 2. The GMLC of claim 1, wherein the determining thecapability is based on service area information of the wireless deviceor is based on velocity information of the wireless device or is basedon both the service area information of the wireless device and thevelocity information of the wireless device.
 3. A method comprising:receiving, by a gateway mobile location center (GMLC) from a locationservices (LCS) client, a request for a capability of a positioningservice level for a wireless device; receiving, by the GMLC from anetwork function, a second message indicating at least one of: apositioning capability of the wireless device; and a positioningcapability of at least one base station; and sending, by the GMLC to theLCS client after receiving the second message, a response comprising thecapability of the positioning service level, wherein the capability ofthe positioning service level comprises a parameter indicating anabsolute or a relative positioning.
 4. The method of claim 3, whereinthe at least one base station is in a registration area of the wirelessdevice.
 5. The method of claim 4, wherein the at least one base stationcomprises a plurality of base stations in the registration area of thewireless device.
 6. The method of claim 3, wherein the second messagefurther comprises service area information of the wireless device. 7.The method of claim 3, wherein the second message further comprisesvelocity information of the wireless device.
 8. The method of claim 3,wherein the capability of the positioning service level indicates asupported positioning service level or a positioning service levelnumber, or both the supported positioning service level and thepositioning service level number.
 9. The method of claim 3, wherein thecapability of the positioning service level comprises a parameterindicating a horizontal accuracy or a vertical accuracy, or both thehorizontal accuracy and the vertical accuracy.
 10. The method of claim3, wherein the capability of the positioning service level comprises aparameter indicating a positioning service availability or a positioningservice latency, or both the positioning service availability and thepositioning service latency.
 11. The method of claim 3, wherein thecapability of the positioning service level comprises a parameterindicating a 5G positioning service area or a 5G enhanced positioningservice area, or both the 5G positioning service area and the 5Genhanced positioning service area.
 12. The method of claim 3, whereinthe request for the capability of the positioning service level for thewireless device and the response comprise an identifier of the wirelessdevice.
 13. A gateway mobile location center (GMLC), comprising: one ormore processors; and memory storing instructions that, when executed bythe one or more processors, cause the GMLC to: receiving, from alocation services (LCS) client, a request for a capability of apositioning service level for a wireless device; receiving, from anetwork function, a second message indicating at least one of: apositioning capability of the wireless device; and a positioningcapability of at least one base station; and sending, by the GMLC to theLCS client after receiving the second message, a response comprising thecapability of the positioning service level, wherein the capability ofthe positioning service level comprises a parameter indicating anabsolute or a relative positioning.
 14. The GMLC of claim 13, whereinthe second message further comprises service area information of thewireless device.
 15. The GMLC of claim 13, wherein the second messagefurther comprises velocity information of the wireless device.
 16. TheGMLC of claim 13, wherein the capability of the positioning servicelevel indicates a supported positioning service level or a positioningservice level number, or both.
 17. The GMLC of claim 13, wherein thecapability of the positioning service level comprises a parameterindicating a horizontal accuracy or a vertical accuracy, or both. 18.The GMLC of claim 13, wherein the capability of the positioning servicelevel comprises a parameter indicating a positioning serviceavailability or a positioning service latency, or both.
 19. The GMLC ofclaim 13, wherein the capability of the positioning service levelcomprises a parameter indicating a 5G positioning service area or a 5Genhanced positioning service area, or both.
 20. The GMLC of claim 13,wherein the request for the capability of the positioning service levelfor the wireless device and the response comprise an identifier of thewireless device.